On 25 April 2016 at 22:03, Jim Wilson <[email protected]> wrote: > On Sun, Apr 24, 2016 at 12:25 PM, Christophe Lyon > <[email protected]> wrote: >> mpfr's config.log contains: >> configure:15555: gcc -o conftest -Wall -Wmissing-prototypes >> -Wpointer-arith -g -O2 -ffloat-store >> -I/home/christophe.lyon/src/bugs/2073/build/MakeRelease/_build/builds/destdir/i686-w64-mingw32/include >> >> -L/home/christophe.lyon/src/bugs/2073/build/MakeRelease/_build/builds/destdir/i686-w64-mingw32/lib >> conftest.c -lgmp >&5 >> /usr/bin/ld: skipping incompatible >> /home/christophe.lyon/src/bugs/2073/build/MakeRelease/_build/builds/destdir/i686-w64-mingw32/lib/libgmp.a >> when searching for -lgmp >> /usr/bin/ld: cannot find -lgmp >> >> I am in an x86_64 jessie chroot. > > It did find a libgmp, it just couldn't use it because it was for a > different target/ABI. > > "gcc" is the wrong compiler for a mingw mpfr build. That should be > i686-w64-mingw32-gcc instead. I see that gmp forces use of -m32 for > the build. That is harmless for the mingw32 compiler which only emits > 32-bit code. But if gmp was also built with "gcc", then you would > have a 32-bit x86-linux libgmp and a 64-bit x86_64-linux libmfpr which > can't be linked together. So I would suspect that they were both > built with the wrong compiler. Not obvious what is wrong, but if you > tried a build with CC=gcc in your environment, then it might fail this > way. >
I do not have such a variable in my environment. Yet, on our Trusty machine we have gcc-mingw-w64 installed (with the i686 and x86_64 variants), but not in the Jessie chroot. That's probably why the build succeeds on Trusty. > Jim _______________________________________________ linaro-toolchain mailing list [email protected] https://lists.linaro.org/mailman/listinfo/linaro-toolchain
