Re: gcc static/dynamic libc default
Olaf Titz (olaf@bigred.inka.de)
Wed, 29 Oct 1997 14:50:12 +0100
> compile another package, which on older machines always uses libc
> dynamically, I find that on the new machine the package gets libc
> statically linked. Even completely re-installing my compiler I still get
> the same result. I am using gcc 2.7.2 on the old machines and on the new
> machine; and the libc is 5.4.38 on all the machines. Is there some kind of
> config file someplace in which one tells gcc whether the libc should be
> linked dynamically or statically? The applciation's own shared library
Your libc is missing a symlink. This is a common problem I've seen a
number of times. Make sure you have both libc.so and libc.so.5
pointing to libc.so.5.4.38 in a place where "ld" can find it (i.e.
/usr/lib).
"ldconfig" doesn't correct this. It makes the libc.so.5 link for
"ld.so", but not the libc.so link for "ld". The last Debian I
installed had this problem for all or at least nearly all libraries in
/usr/lib. This can also make certain configure scripts fail.
olaf