Re: ld links static after upgrading libc
Alessandro Suardi (asuardi@uninetcom.it)
Tue, 14 Jan 1997 21:31:43 +0100
Kristofer T. Karas wrote:
>
[snipped my stuff]
> In order for `ld' to make a shared library reference rather than
> statically include code, it must find the libFOO.so file before it
> finds the libFOO.a file; unless you know the search order, the
> convention is to put both in the same directory. Hence, you should
> have:
>
> /lib/libc.so.5 -> /lib/libc.so.5.4.17 # Built automatically by ldconfig.
> /usr/lib/libc.so -> /lib/libc.so.5 # Built by hand.
> /usr/lib/libc.a # Normal location of libc.a
>
My ld looks for /usr/lib/libc.so.5. I don't have the /usr/lib/libc.so
link and I link shared. XFree86 3.2 was linked a couple of weeks ago
with no problem at all. I remember getting to that setup after a strace
of ld. I guess it's one of the possibilities you have.
Cheers,
--alessandro <asuardi@uninetcom.it> <asuardi@it.oracle.com>
Linux kernel-2.1.20 libc-5.4.17 gcc-2.7.2.1 binutils-2.7.0.3