"Dennis Clarke" <dclarke@xxxxxxxxxxxxx> writes: > Both GMP and MPFR are built and pass all tests and the libraries are created > fine : > > gmp-4.2.2 > mpfr-2.3.1 > > dclarke@vesta:~/build/first_pass/gcc/gcc-4.2.3-build$ ls -lap > $HOME/local/lib | grep -E "gmp|mpfr" > -rw-r--r-- 1 dclarke csw 592016 Mar 9 17:48 libgmp.a > -rwxr-xr-x 1 dclarke csw 794 Mar 9 17:48 libgmp.la > lrwxrwxrwx 1 dclarke csw 15 Mar 9 17:48 libgmp.so -> libgmp.so.3.4.2 > lrwxrwxrwx 1 dclarke csw 15 Mar 9 17:48 libgmp.so.3 -> libgmp.so.3.4.2 > -rwxr-xr-x 1 dclarke csw 317869 Mar 9 17:48 libgmp.so.3.4.2 > -rw-r--r-- 1 dclarke csw 1812424 Mar 9 22:06 libmpfr.a > -rwxr-xr-x 1 dclarke csw 985 Mar 9 22:06 libmpfr.la > lrwxrwxrwx 1 dclarke csw 16 Mar 9 22:06 libmpfr.so -> libmpfr.so.1.1.1 > lrwxrwxrwx 1 dclarke csw 16 Mar 9 22:06 libmpfr.so.1 -> libmpfr.so.1.1.1 > -rwxr-xr-x 1 dclarke csw 985371 Mar 9 22:06 libmpfr.so.1.1.1 You will do better to use --disable-shared when you configure gmp and mpfr. Using the shared libraries means that you need to ensure that gcc can find them at runtime, and that typically requires setting LD_LIBRARY_PATH. > /home/dclarke/local/powerpc-unknown-linux-gnu/sys-include accepts -g... no > checking whether the GNU Fortran compiler is working... no > configure: error: GNU Fortran is not working; the most common reason for > that is that you might have linked it to shared GMP and/or MPFR libraries, > and not set LD_LIBRARY_PATH accordingly. If you suspect any other reason, > please report a bug in http://gcc.gnu.org/bugzilla, attaching > /home/dclarke/build/first_pass/gcc/gcc-4.2.3-build/powerpc-unknown-linux-gnu/libgfortran/config.log There you go: set LD_LIBRARY_PATH to work around this, but even better is to use static gmp and mpfr libraries. > Should I just set LD_LIBRARY_PATH=$HOME/local/lib ?? That will probably work too. Ian
