<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Tue, 2010-09-21 at 14:50 -0700, Alan Coopersmith wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">libtool 2.x is better than 1.x, which made it impossible to correctly</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">build 64-bit libraries on Solaris, since it hardcoded in the libtool</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">script the ld flag for 64-bit builds, and thus failed when using</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">$(LD)=$(CC) as recommended to ensure the right language-specific</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">bits/flags are passed to the linker by the compiler.</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
We just had a discussion about making libtool v2 the minimum required version.<BR>
I did not investigate thoroughly, but when the module as an m4 directory libtool copies<BR>
its macros there and they are used on system with v 1.5. So as long as the tarball<BR>
is created with v2, you know it won't be linked using v1.5. Unless of course someone autoreconf<BR>
the tarball with v1.5. <BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">I've still had other problems with 2.x deciding to drop linker options</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">it didn't want me to use. And of course, hacking install.sh to never</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">install a .la file improves things a lot.</FONT></TT><BR>
</BLOCKQUOTE>
AC_DISABLE_STATIC (called before AC_PROG_LIBTOOL) should do that, or calling ./configure<BR>
with --disable-static. Sorry, I can only suggests trivial solutions.
</BODY>
</HTML>