Re: Problem with libc6-pic
Hi Rene,
can you forward me the whole thread, please? I am not sure I have the
start of it. I saw this by luck, it would have been good to CC me.
It might be that mklibs.sh is not including weak symbols. I can probably
tell more when I have the whole thread and did some tests at home.
glibc is a very complex library, and with each new major glibc version,
mklibs.sh needs some tweaks. It works surprisingly well for its
simplicity, at the cost of a little manual maintenance necessary.
Recently a bug was discovered for g++ using libs, but this is
a different one, I think.
Thanks,
Marcus
Am Die, 31 Okt 2000 12:07:13 schrieb Rene Mayrhofer:
> Ben Collins wrote:
> > On Mon, Oct 30, 2000 at 07:55:37PM +0100, Rene Mayrhofer wrote:
> > > Ben Collins wrote:
> > > > objdump --dynamic-syms bin/busybox | grep lxstat
> > > >
> > > > Send me the output from that please.
> > > 080496cc DF *UND* 00000137 GLIBC_2.0 __lxstat
> >
> > Strange, busybox is showing it doesn't use lxstat64 (which is what I
> > expected, but it is still strange :)
> >
> > > Does this mean that it only needs glibc 2.0 ? There are only 2 symbols
tagged
> > > with glibc 2.1:
> > > 0804979c DF *UND* 0000016a GLIBC_2.1 fclose
> > > 0804993c DF *UND* 0000009f GLIBC_2.1 fopen
> >
> > Ok, this is from libc.so.6:
> >
> > 00000000000c800c g DF .text 0000000000000100 (GLIBC_2.1) __lxstat64
> > 00000000000c7c34 g DF .text 00000000000000fc GLIBC_2.0 __lxstat
> > 00000000000c800c g DF .text 0000000000000100 GLIBC_2.2 __lxstat64
> >
> > So the most recent lxstat64 is the GLIBC_2.2 one, which is the one that
> > should get used if anything links with it. Now the question is, where does
> > this come from? __lxstat64@GLIBC_2.1 is a weak symbol (only there for
> > backward compatibility).
> >
> > IMO, this might just be a bug in mkshlibs.sh
> Great :-(
> Does anybody besides Markus Brinkmann know the script well enough to debug it
?
> I certainly do not. Does it work on your system ? Can you build a minimized
> libc6 for busybox ?
> Am I the only one experiencing this problem at the moment ?
>
> best greets,
> Rene
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
Reply to: