[lkml]   [1997]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ld links static after upgrading libc
   Date: 	Mon, 13 Jan 1997 19:53:04 +0100
From: Alessandro Suardi <>

Chris Y. wrote:
> I seem to be having a problem that I can't explain.

Check symlinks. You should have:
/lib/ -> /lib/
/lib/ -> /lib/
/usr/lib/ -> /lib/

You got two of those backwards. The goes in the same
directory as libc.a, namely /usr/lib (not /lib). And the in
the /usr/lib directory has no effect, as the linker won't look for it
there (it will look for it in the same directory as the

In order for `ld' to make a shared library reference rather than
statically include code, it must find the 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

/lib/ -> /lib/ # Built automatically by ldconfig.
/usr/lib/ -> /lib/ # Built by hand.
/usr/lib/libc.a # Normal location of libc.a

Kristofer Karas - Sr Clinical Sys Admin - Beth Israel Deaconess Medical Center
AMA/CCS, DoD, RF900RR, HawkGT, !car - Will design LISP machines for food :-)
"Health nuts are going to feel stupid someday, lying in hospitals dying
of nothing." -- Redd Foxx

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