This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Fix libjava x86-64 multilib
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Michael Matz <matz at suse dot de>
- Cc: Bo Thorsen <bo at sonofthor dot dk>, <gcc-patches at gcc dot gnu dot org>
- Date: 02 Oct 2002 17:00:51 -0300
- Subject: Re: Fix libjava x86-64 multilib
- Organization: GCC Team, Red Hat
- References: <Pine.LNX.4.33.0210021104330.22516-100000@wotan.suse.de>
On Oct 2, 2002, Michael Matz <matz@suse.de> wrote:
> In the end we are most often better off simply using pass_all, and
> rely on the linker to tell us if something went wrong, and fix the
> PIC flags for the causing objects.
Feel free to use pass_all when you want to pinpoint what's going on.
Libtool's semantics matches its documented behavior (which you
describe quite well), even if it's not always what one desire being
used to platforms in which shared libraries are available and can
contain non-PIC.
The problem of distinguishing non-PIC from PIC in library.a is a real
one, for which there's no solution in sight, but pass_all must not be
the default in libtool if it will cause linker failures.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer