severity 321561 critical merge 321561 322768 severity 321712 critical merge 321712 322768 tags 323032 unreproducible thanks On Sun, Aug 14, 2005 at 05:54:30AM -0400, simon raven wrote: > Package: libc6 > Version: 2.3.2.ds1-22 > Severity: grave > Justification: renders package unusable > fakeroot debian/rules binary > /usr/bin/make: relocation error: /lib/libdl.so.2: symbol _dl_catch_error, version GLIBC_PRIVATE not defined in file ld.so.1 with link time reference > zsh: 8307 exit 127 fakeroot debian/rules binary > this is a follow-up to 321561 and 321712. if i allow the upgrade to > happen, i can't even run make, or perl, or crond, or anything at all in > fact. please fix this. Except that in fact, this bug is not the same as those other two bugs. Bugs #321561 and 321712 are problems with daemons running after glibc upgrade resulting from internal interface changes in glibc. make is not a daemon, so that is not the same bug. However, $ dpkg -x g/glibc/libc6_2.3.5-3_powerpc.deb /tmp/libc6 $ nm -Du /tmp/libc6/lib/libdl.so.2 |grep _dl_catch_error $ I can't find any evidence of this bug you're describing in glibc 2.3.5-3. Since the version header in this bug report is known to be incorrect, I can't say with any certainty where this bug is coming from, but I can say that it is *not* in glibc 2.3.5-3 based on the above commands. If anything, though, it looks like you've managed to screw up your system somehow in the upgrade process and get a libdl.so.2 from glibc 2.3.2 together with the ld.so from glibc 2.3.5. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature