public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "windward at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53798] [4.7] Bootstrap fails on Linux x86_64 with pre-built libmpc/mpfr/gmp due to multilib path problem
Date: Tue, 17 Jul 2012 13:41:00 -0000	[thread overview]
Message-ID: <bug-53798-4-bmpiZTE3Li@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53798-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53798

--- Comment #8 from Martin <windward at gmx dot com> 2012-07-17 13:41:35 UTC ---
(In reply to comment #7)

> And what about when you put gmp, mpfr and mpc in the GCC source tree? That's
> what worked fine for me.  The same configure command without the
> --with-gmp/--with-mpfr/--with-mpc options?
Yep, tried that, failed with undefined references (see comment #3). To be
perfectly honest I did not investigate further since the workaround lets the
build run fine with the pre-compiled libs.

> The GCC binaries use GMP, MPFR and MPC internally and the GCC binaries are
> only built for a single arch, even if they are capable of producing multilib
> output.  I don't know but I guess libjava now uses them too, and so multilib
> libjava needs multilib support libs.
Seems so, I never had to provide 32 bit GMP, MPFR and MPC before.
But I rather had libtool in mind. I have never seen it providing a complete
path- and filename when calling the linker. I suppose fixing that will solve
the whole thing - at least with GNU ld, which will pick the right lib if 32 and
64 bit lib paths are given with -L.

> (In reply to comment #6)
> > --with-gnu-as --with-as=/opt/SP/gcc/gcc-4.7.1/bin/as \
> > --with-gnu-ld --with-ld=/opt/SP/gcc/gcc-4.7.1/bin/ld
> That's redundant, if configure finds an assembler and linker in the
> installation directory it will use them.
Errrm... well, yeah. I have _one_ rather large script to build GCC for Solaris
SPARC & x86 and Linux x86. In fact these parameters are env vars, and on
Solaris the linker settings would point to /usr/ccs/bin/ld (without-gnu-ld),
even though the GNU ld is present in the installation dir. Besides that there
are other versions in the PATH, so I prefer not to rely on smart configure
scripts. But thanks for pointing out.


  parent reply	other threads:[~2012-07-17 13:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 14:12 [Bug bootstrap/53798] New: " windward at gmx dot com
2012-06-28 14:31 ` [Bug bootstrap/53798] " redi at gcc dot gnu.org
2012-07-17 10:10 ` windward at gmx dot com
2012-07-17 10:11 ` windward at gmx dot com
2012-07-17 10:46 ` redi at gcc dot gnu.org
2012-07-17 12:16 ` windward at gmx dot com
2012-07-17 12:18 ` windward at gmx dot com
2012-07-17 12:35 ` redi at gcc dot gnu.org
2012-07-17 13:41 ` windward at gmx dot com [this message]
2013-02-26 14:22 ` windward at gmx dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-53798-4-bmpiZTE3Li@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).