Re: question about overriding ld.so.conf
On Sun, Jun 05, 2011 at 10:20:06AM +0200, Harald Dunkel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Aurelien, Hi, On 06/04/11 13:06, Aurelien Jarno wrote: I do think it is reasonable. The idea behind hwcap or osversion is to provide two versions of the same libraries and select the right one at runtime depending on the hardware or kernel capabilities. I see. But what if there are 2 versions of the same library on the same compatibility level, coming from different vendors? Vendor A uses the os abi tag (setting it to 2.4.20, which was +8 years ago), and vendor B doesn't care about ancient systems and doesn't set this tag. Obviously there is something wrong. As a consumer, how can I fix this and get the library I want? (I know strip, but that would be cheating.) I think the problem has to be fixed in the libraries themselves, this can be done in two ways: - the library not providing an os abi tag should be changed to provide one. - the library providing an (outdated) os abi tag should not be provided. As a consumer, here are the things you can do: - Remove the os abi tag stripping the library - Removing the wrong library, or replace the wrong one by the good one - Use LD_LIBRARY_PATH with the path to the right library. It gets priority over os abi tag. Aurelien -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607110015.gb5...@ohm.aurel32.net
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Package: libc6 Version: 2.13-5 Severity: critical Justification: breaks the whole system While upgrading from libc6 2.13-4 to 2.13-5 on a i386 system: Preparing to replace libc6 2.13-4 (using .../archives/libc6_2.13-5_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.13-5) ... Installing new version of config file /etc/ld.so.conf.d/i486-linux-gnu.conf ... Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi' E: Sub-process returned an error code E: Sub-process /usr/bin/dpkg returned an error code (127) After this no dynamically linked program on the system is startable anymore: haegar:~# dpkg --help Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! haegar@aurora:~$ ls Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-sdinet14-aurora (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libc6 depends on: ii libc-bin 2.13-4 Embedded GNU C Library: Binaries ii libgcc1 1:4.6.0-11 GCC support library Versions of packages libc6 recommends: ii libc6-i6862.13-4 Embedded GNU C Library: Shared lib Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.39 Debian configuration management sy ii glibc-doc 2.13-4 Embedded GNU C Library: Documentat ii locales 2.13-4 Embedded GNU C Library: National L -- debconf-show failed -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607140411.6858.77273.reportbug@aurora.local
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Hi Sven, Sven-Haegar Koch wrote: While upgrading from libc6 2.13-4 to 2.13-5 on a i386 system: Preparing to replace libc6 2.13-4 (using .../archives/libc6_2.13-5_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.13-5) ... Installing new version of config file /etc/ld.so.conf.d/i486-linux-gnu.conf ... Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! Very odd. That assertion doesn't exist in current glibc; in fact, it was was removed in glibc 2.3! (cvs/glibc-2-3~925, elf/dynamic-link.h (elf_get_dynamic_info): Don't abort on unknown dynamic tags, 2002-04-03). But it was in an inline function in that header, so if some binary package was built on a machine with ancient libc6-dev, that could be a half-explanation. Where do you get your binary packages from? Puzzled, Jonathan -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607144656.GA13080@elie
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Just to confirm that Sven is not alone, I was hit by the same bug.
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Dima wrote: Just to confirm that Sven is not alone, I was hit by the same bug. Thanks. To be clear, that means you are also on i386 and also trigger the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5? I tried reproducing this in a debian-live i386 installation but I didn't manage (the upgrade to libc6-i686 2.13-5 proceeded without trouble). What I said before about libc6-dev was nonsense; elf/dynamic-link.h is a file in the eglibc source package, which makes this all the more puzzling (how was this assertion from more than 5 years ago resurrected?). Probably I am missing something obvious. :) -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607154947.GA24770@elie
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Thanks. To be clear, that means you are also on i386 and also trigger the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5? That's right. I'm still logged into the box remotely, but I can not start any new processes. Regards, Dima.
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
But it was in an inline function in that header, so if some binary package was built on a machine with ancient libc6-dev, that could be a half-explanation. Where do you get your binary packages from? ftp.de.debian.org I also get my packages from ftp.de.debian.org But the system has been updated on Debian Unstable since Debian Woody (and moved from PC to PC, from harddisk to harddisk, without reinstall). Mine is also quite old, I've been running unstable for the last 10 years. Regards, Dima.
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
On Tue, 7 Jun 2011, Dima wrote: But it was in an inline function in that header, so if some binary package was built on a machine with ancient libc6-dev, that could be a half-explanation. Where do you get your binary packages from? ftp.de.debian.org I also get my packages from ftp.de.debian.org But the system has been updated on Debian Unstable since Debian Woody (and moved from PC to PC, from harddisk to harddisk, without reinstall). Mine is also quite old, I've been running unstable for the last 10 years. Just to verify - could you check if you also have got an /lib/ld.so file? As you wrote that you are still logged into it you should be able to do the following: $ cd /lib $ echo ld* (and then looking in the output) c'ya sven-haegar -- Three may keep a secret, if two of them are dead. - Ben F. -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.02.1106071842300.27505@aurora
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
As you wrote that you are still logged into it you should be able to do the following: $ cd /lib $ echo ld* Here is is: $ echo ld* ld-2.2.5.so ld-linux.so.1.8.10 ld-linux.so.2 ld.so ld.so.1.8.10
Bug#629556: please provide getvfsbyname()
Package: libc0.1-dev Version: 2.13-4 Severity: wishlist FreeBSD libc provides getvfsbyname() function, which is used by NFS userland code. It can't be provided by libbsd because it's kFreeBSD-specific: http://svnweb.freebsd.org/base/head/lib/libc/gen/getvfsbyname.c -- System Information: Debian Release: 6.0.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.2-1-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc0.1-dev depends on: ii kfreebsd-kernel-headers 0.55 kernel of FreeBSD headers for deve ii libc-dev-bin 2.13-4 Embedded GNU C Library: Developmen ii libc0.1 2.13-4 Embedded GNU C Library: Shared lib Versions of packages libc0.1-dev recommends: ii gcc [c-compiler] 4:4.6.0-5 The GNU C compiler ii gcc-4.6 [c-compiler] 4.6.0-11 The GNU C compiler Versions of packages libc0.1-dev suggests: pn glibc-doc none (no description available) pn manpages-dev none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607175424.27671.31813.reportbug@dimoni
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
I believe I hit the same bug on amd64. After upgrading, all commands fail with error while loading shared libraries: /lib/x86_64-linux-gnu/libc.so.6: unexpected PLT reloc type 0x25. /lib/ld-linux-x86-64.so.2 is pointing to a rather old ld-lsb-x86-64.so.3, changing it to point to x86_64-linux-gnu/ld-2.13.so fixes the problem. Regards, -Atte -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTina_U69e73=aawark+xp7klvo8...@mail.gmail.com
r4716 - in glibc-package/trunk/debian: . testsuite-checking
Author: sthibault Date: 2011-06-07 21:43:53 + (Tue, 07 Jun 2011) New Revision: 4716 Modified: glibc-package/trunk/debian/changelog glibc-package/trunk/debian/testsuite-checking/expected-results-i486-gnu-libc glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i386 glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i686 glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-xen Log: Update expected hurd-i386 failures. Modified: glibc-package/trunk/debian/changelog === --- glibc-package/trunk/debian/changelog2011-06-06 17:34:37 UTC (rev 4715) +++ glibc-package/trunk/debian/changelog2011-06-07 21:43:53 UTC (rev 4716) @@ -7,6 +7,9 @@ asm-sparc64. Use the multiarch asm directory if present. * debian/copyright: update. + [ Samuel Thibault ] + * Update expected hurd-i386 failures. + -- Aurelien Jarno aure...@debian.org Sun, 05 Jun 2011 00:27:40 +0200 eglibc (2.13-5) unstable; urgency=low Modified: glibc-package/trunk/debian/testsuite-checking/expected-results-i486-gnu-libc === --- glibc-package/trunk/debian/testsuite-checking/expected-results-i486-gnu-libc 2011-06-06 17:34:37 UTC (rev 4715) +++ glibc-package/trunk/debian/testsuite-checking/expected-results-i486-gnu-libc 2011-06-07 21:43:53 UTC (rev 4716) @@ -75,6 +75,8 @@ tst-timer.out, Error 1 tst-tls18.out, Error 1 tst-tls9-static.out, Error 1 +tst-unique1.out, Error 1 +tst-unique2.out, Error 127 tst-vfork3-mem, Error 1 tststatic.out, Error 139 tststatic2.out, Error 139 Modified: glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i386 === --- glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i386 2011-06-06 17:34:37 UTC (rev 4715) +++ glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i386 2011-06-07 21:43:53 UTC (rev 4716) @@ -75,6 +75,8 @@ tst-timer.out, Error 1 tst-tls18.out, Error 1 tst-tls9-static.out, Error 1 +tst-unique1.out, Error 1 +tst-unique2.out, Error 127 tst-vfork3-mem, Error 1 tststatic.out, Error 139 tststatic2.out, Error 139 Modified: glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i686 === --- glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i686 2011-06-06 17:34:37 UTC (rev 4715) +++ glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-i686 2011-06-07 21:43:53 UTC (rev 4716) @@ -75,6 +75,8 @@ tst-timer.out, Error 1 tst-tls18.out, Error 1 tst-tls9-static.out, Error 1 +tst-unique1.out, Error 1 +tst-unique2.out, Error 127 tst-vfork3-mem, Error 1 tststatic.out, Error 139 tststatic2.out, Error 139 Modified: glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-xen === --- glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-xen 2011-06-06 17:34:37 UTC (rev 4715) +++ glibc-package/trunk/debian/testsuite-checking/expected-results-i686-gnu-xen 2011-06-07 21:43:53 UTC (rev 4716) @@ -75,6 +75,8 @@ tst-timer.out, Error 1 tst-tls18.out, Error 1 tst-tls9-static.out, Error 1 +tst-unique1.out, Error 1 +tst-unique2.out, Error 127 tst-vfork3-mem, Error 1 tststatic.out, Error 139 tststatic2.out, Error 139 -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qu441-bh...@vasks.debian.org
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
retitle 629534 Upgrade fails, resulting in unusable system (no dynamic linking) thank you On Tue, 7 Jun 2011 10:49:48 -0500, Jonathan Nieder jrnie...@gmail.com wrote: Just to confirm that Sven is not alone, I was hit by the same bug. Me too! Thanks. To be clear, that means you are also on i386 and also trigger the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5? I am also on i386 and also hit the failure on upgrade from 2.13-4 to 2.13-5. I did not see the bad dynamic tag assertion failure. Elsewhere in the thread was discussion of old linkers in /lib. I had that as well: /lib$ echo ld* ld-2.7.so ld-linux.so.2 I was able to fix my system by booting to a live USB, mounting my filesystem and updating that symlink: ln -sf i386-linux-gnu/ld-2.13.so /lib/ld-linux.so.2 I saw that some people were having trouble replicating the upgrade failure. In case it helps, here is the upgrade history I was able to find for the libc6 package on my system: 2010-10-12: libc6:i386 (2.11.2-5, 2.11.2-7) 2011-01-11: libc6:i386 (2.11.2-6, 2.11.2-7) 2011-05-23: libc6:i386 (2.11.2-7, 2.11.2-11) 2011-05-05: libc6:i386 (2.11.2-11, 2.13-2) 2011-05-24: libc6:i386 (2.13-2, 2.13-4) Please let me know if there's any further information I can provide. -Carl -- carl.d.wo...@intel.com pgpNsxQwKUt0r.pgp Description: PGP signature
Processed: Re: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Processing commands for cont...@bugs.debian.org: retitle 629534 Upgrade fails, resulting in unusable system (no dynamic linking) Bug #629534 [libc6] libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore Changed Bug title to 'Upgrade fails, resulting in unusable system (no dynamic linking)' from 'libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore' thank you Stopping processing here. Please contact me if you need assistance. -- 629534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130748593530632.transcr...@bugs.debian.org
