Re: xlib6g and emacs (and others)
On Tue, Sep 09, 1997 at 07:38:35PM -0400, Joey Hess wrote:
> Ok, I've got the nextaw libc5 compat package built, and libc5 apps do use
> it. But the thing depends on both libc5 and libc6:
> joey@kite:~/debian/build/nextaw-0.5.1/libc5-compat>ldd ./libneXtaw.so.6
> libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40058000)
> libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x4006a000)
> libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x400b2000)
> libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x400bb000)
> libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400d0000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400dc000)
> libc.so.5 => /lib/libc.so.5 (0x40180000)
> libc.so.6 => /lib/libc.so.6 (0x4023e000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)
> Now I built this with the following command line:
> So first of all, I don't understand why ldd shows it linked against
> /usr/X11R6/lib/libX11.so.6 ,etc.
> And I'm also puzzled why all the libraries in /usr/lib/libc5-compat/ seem to
> be linked to libc6.
I suspect it is built correctly. What you are seeing is a misfeature
of ldd when dealing with shared libraries and, unfortunately, there is
no easy way to fix it.
The problem is that ldd uses the libc6 dynamic linker when it is run
on shared libraries because the older way I used to do it was broken.
As a result, depenencies are searched as if they are need for a libc6
program. In your case, this causes the libc6-based X libs to be found
which also brings in libc6.
I'll think about the problem, but I'm not sure how soon or even if I
can come up with a good solution.
David Engel ODS Networks
email@example.com 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .