On Jul 19, 2000, Chris <[EMAIL PROTECTED]> wrote:
> Alexandre Oliva wrote:
>>
>> On Jul 19, 2000, Paul Berrevoets <[EMAIL PROTECTED]> 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?
On most systems, you can't include non-PIC code in shared libraries
and, when you can, the libraries become extremely inefficient.
> Libtool really should provide a warning, and not remove those static
> libraries.
Feel free to submit patches to do that. I can't assure you they'll be
installed, though.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
