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: Jakub Jelinek <jakub at redhat dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Bo Thorsen <bo at sonofthor dot dk>, gcc-patches at gcc dot gnu dot org
- Date: Wed, 2 Oct 2002 03:18:10 -0400
- Subject: Re: Fix libjava x86-64 multilib
- References: <200210012044.41032.bo@sonofthor.dk> <orfzvpycop.fsf@free.redhat.lsd.ic.unicamp.br>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Tue, Oct 01, 2002 at 08:14:14PM -0300, Alexandre Oliva wrote:
> On Oct 1, 2002, Bo Thorsen <bo@sonofthor.dk> wrote:
>
> > This fixes the multilib error I've been getting. Bootstrapped on x86-64
> > (finally!). Can I commit it?
>
> Wow! Is LD really used by libtool on x86_64*linux*? I'm surprised.
> Do you have a pointer to the message in which you give more details
> about the problem? I must have missed it :-(
>
> > 2002-10-01 Bo Thorsen <bo@suse.de>
>
> > * configure: rebuilt after toplevel libtool.m4 fix.
>
> > 2002-10-01 Bo Thorsen <bo@suse.de>
>
> > * libtool.m4: Fix x86-64 multilib
>
> Please make sure this makes it to libtool CVS if it's not there yet.
> As soon as it makes it there, it's ok to install it in GCC and src
> too.
Furthermore, if the first hunk is really necessary, it should be done
similarly for sparc*linux*, ppc*linux* and s390*linux*.
Wonder why ld -r was apparently never run when I was building libgcj
on sparc64.
Jakub