On 19-Jul-2000 Chris wrote:
>> > On Solaris, libtool does not allow me to do the following:
>> >> /bin/sh ../libtool --mode=link gcc -g -O2 -o libfoo.la -rpath
>> > /usr/local/lib foo.lo /usr/local/lib/libbar.a
>> > libtool: link: cannot build libtool library `libfoo.la' from non-libtool
>> > objects: /usr/local/lib/libbar.a
>> Libtool is right. It can't be done portably, so libtool won't do it
>> for you.
> I asked the same question a while back, and got pretty much the same
> answer. The question that I have is, "where" is this not done
> portable? I have worked around the libtool to force static libraries
> into shared libraries, and I drop those static stuffed shared libraries
> onto our other machines (Solaris), and they work just fine. So I'd say,
> Libtool is only partly right. Libtool really should provide a warning,
> and not remove those static libraries.
Yep. That's already implemented in CVS libtool:
2000-01-19 Thomas Tanner <[EMAIL PROTECTED]>
* ltmain.in: rewrite of the ILD code, merge linking code for
programs, libraries and objects, allow linking of shared libraries
against static libraries/objects on platforms that support it
but print a warning, fix some typos
Thomas Tanner -------------------------
email: tanner@(ffii.org|gnu.org|gmx.de)
web: http://home.pages.de/~tanner
UMI: http://umi.ffii.org
