http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53798
--- Comment #5 from Martin <windward at gmx dot com> 2012-07-17 12:15:38 UTC ---
IMHO nothing special with the configure call.
SRCDIR=/opt/SP/build/gcc/gcc-4.7.1
Build dir=/opt/SP/build/gcc/gcc-4.7.1-build
INSTPATH=/opt/SP/gcc/gcc-4.7.1
A set of tools including current binutils have been built & installed in
$INSTPATH beforehand, especially libgmp, libmpfr and libmpc. 64 bit libs in
${INSTPATH}/lib64, 32 bit in ${INSTPATH}/lib.
${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
The bootstrapping worked perfectly before (4.4-4.6) with the same script, I
just didn't have to build 32 bit MPC, MPFR and GMP libs (and obviously did not
use the corresponding parameters).
The crude workaround in my last attachment works fine as long as LDFLAGS and
LD_LIBRARY_PATH include both ${INSTPATH}/lib64 and ${INSTPATH}/lib. If the
configure script adds _any_ "-Lpath" to $gmplibs / GMPLIBS, libtool will mess
up the linker call by adding the library with full path and filename. If this
wasn't the case, the configure parameters as given above should work.
Any idea why this happens, and only with libjava?
BR Martin
