http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53662
Leif Leonhardy <bugfeed at online dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugfeed at online dot de
--- Comment #4 from Leif Leonhardy <bugfeed at online dot de> 2012-11-26
04:01:07 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> >
> > That means you need a 64-bit capable binutils.
> >
> > Just a guess, but you might need to use --target=x86_64-unknown-linux-gnu to
> > make a cross compiler for x86_64, which will be multilib-capable by
> > default.
> > To do that you'll need a 64-bit binutils and 64-bit glibc.
> >
> > This should really be dealt with on the gcc-help mailing list, I don't think
> > it's a bug.
>
> Sorry, I meant that this might be bug in gcc bootstrap stage. As I said, I
> have
> compiled binutils with --enable-multilib ... I could try --enable-64-bit-bfd
> tough.
That's not what you /could try/, that's what you *have to* do... ;-)
I.e., configure binutils with '--enable-64-bit-bfd --enable-targets=all'
(e.g.), otherwise the built 'gas' bails out on '--64'.
-leif
P.S.: I'm currently trying to build a "multilib" GCC 4.7.2 on a Pentium4
(a.k.a. i786), i.e., x86 system. Build goes fine until libquadmath's
'configure' tries to *run* executables built with '-m64' (which of courseTM
cannot work). No idea why it's attempting that -- probably because
host==build==target==pentium4-linux-gnu and it doesn't notice that we're
"cross-compiling" in the 64/ directory. The other libs built just fine (e.g.
libssp).
