Bug#156157: libc6: Several _dl_ symbols cannot be resolved.
> binutils_2.12.90.0.14-1_i386.deb
> libc6_2.2.5-12_i386.deb
> libc6-dev_2.2.5-12_i386.deb
> gcc-2.95_1%3a2.95.4-10_i386.deb
bmc> These are known to work perfectly well.
"Known perfect" is an awfully strong phrase under the circumstances.
Especially since downgrading to binutils_2.11.92.0.12.3-4_i386.deb
that happened to be lying around allows me to build the trivial
example. (I've upgraded the other packages mentioned to the most
recent I could find, specifically
ii libc6 2.2.5-13 GNU C Library: Shared libraries and Timezone
ii gcc 2.95.4-16 The GNU C compiler.
ii gcc-2.95 2.95.4-11 The GNU C compiler.)
I'm fairly sure I was able to build with
binutils_2.12.90.0.13-1_i386.deb, and I know I was at
binutils_2.12.90.0.09-1_i386.deb for quite a while. So it's probably
some interaction between my system's configuration and something that
happened in those recent revisions.
Can you move/broaden this bug to binutils, or should I file a new one
and cross-reference this one?
bmc> I get the same result on all my systems, and they all work
bmc> fine. Is /lib/ld-linux.so.2 a symlink to /lib/ld-2.2.5.so?
Yes.
Best regards,
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py
Reply to: