FS#30978 - pacman links against libcurl, which breaks when upgraded without glibc
Attached to Project:
Arch Linux
Opened by James Kay (Twey) - Thursday, 02 August 2012, 16:40 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 02 August 2012, 18:03 GMT
Opened by James Kay (Twey) - Thursday, 02 August 2012, 16:40 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 02 August 2012, 18:03 GMT
|
Details
Description:
I recently upgraded my system according to https://wiki.archlinux.org/index.php/DeveloperWiki:usrlib , but upgrading curl without first upgrading glibc (as suggested there) results in breaking pacman with the error: pacman: /lib/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib/libcurl.so.4) A workaround is to use LD_PRELOAD to preload a working version of libcurl.so. Additional info: glibc 2.15-11 (to be upgraded to 2.16) pacman 4.0.3-3 curl 7.26.0-1 (to be upgraded to 7.27.0-1) Steps to reproduce: 1) Install glibc <2.16 and a matching curl. 2) Upgrade curl without upgrading glibc. 3) Attempt to run pacman. |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 02 August 2012, 18:03 GMT
Reason for closing: Not a bug
Additional comments about closing: Nothing to do here. Wiki has been updated for slackers.
Thursday, 02 August 2012, 18:03 GMT
Reason for closing: Not a bug
Additional comments about closing: Nothing to do here. Wiki has been updated for slackers.
> Why pacman is not statically linked?
If you'd look into this, you'd see that static linkage with glibc is difficult if not impossible, particularly when network symbols are involved. Even a "static linked" pacman would still require the presence of a matching glibc for a few symbols.