lkml.org 
[lkml]   [1997]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ld links static after upgrading libc
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



\
 
 \ /
  Last update: 2005-03-22 13:38    [W:0.097 / U:0.356 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site