http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53798
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-07-17
12:35:39 UTC ---
(In reply to comment #5)
> ${SRCDIR}/configure --prefix=${INSTPATH} \
> --with-gmp=${INSTPATH} --with-mpfr=${INSTPATH} --with-mpc=${INSTPATH} \
> --with-gmp-lib=${INSTPATH}/lib64 --with-libelf=${INSTPATH} \
> --with-gnu-as --with-as=/opt/SP/gcc/bin/as \
> --with-gnu-ld --with-ld=/opt/SP/gcc/bin/ld
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?
> Any idea why this happens, and only with libjava?
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.
(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.
