Re: Bug in generation of static link lines for three specific libraries

[Noah Misch]

On Thu, May 17, 2007 at 11:50:34AM -0400, Eric S. Raymond wrote:
> Somewhere deep inside either the libtool/autotools/automake toolchain,
> there appears to be a bug relating to generation of command-line references
> for three specific static libraries.

Libtool is responsible for the behavior you describe; you can exclude
address@hidden from followups.

> What these have in common is that for three modules, 
> 
> /usr/lib/libgmodule-2.0.so /usr/lib/libgthread-2.0.so /usr/lib/libglib-2.0.so
> 
> something in the toolchain is generating references to dynamic libs when 
> static
> libs were desired.

It looks like the system integrator built these libraries with --disable-shared.
Do any of /usr/lib/libg{module,thread,lib}-2.0.a exist?  If so, please post the
contents of /usr/lib/libglib-2.0.la.  If not, you will need copies of these
static libraries to link a static application that needs them.

Libtool currently tries to use a dynamic library when there is no static library
available, even when attempting a fully static link.  I imagine this fails on
most systems.  It should probably print a message and fail, instead.