./configure: syntax error at line 20: `(' unexpected
2. Q:
The configure reports the compiler as being broken, but there is
no problem with the compiler (it runs the test that supposedly failed without
trouble).
A:
You may be using the Bash shell (/bin/bash) as a replacement for
the Bourne shell (/bin/sh). We have reports that, at least under
LINUX, Bash does not properly handle return codes in expressions. One fix is
to use a different shell, such as /bin/ash, on those systems.
This won't work on some LINUX systems ( every shell is broken). We have reports that the following will work:
checking gnumake... 1: Bad file number
4. Q: Configure reports that floating point is not commutative! How do I
fix it?
A:
Check your compiler's documentation. On RS/6000's, the -qnomaf (no
multiply-add floating point) option. On some other systems, intermediate
results may be stored in 80-bit registers (Intel CPUs do this); this can also
lead to inconsistent rounding. You may be able to force the compiler to
round to 64 bits.
checking that the compiler f77 runs... no Fortran compiler returned non-zero return code Output from test was f2ctmp_conftest.f: MAIN main:
To fix this problem, you need a corrected f77 script. If you can edit
the script yourself, change the last 3 lines from
case $cOPT in 2) $CC $G -o $OUTF $OFILES -lf2c -lm;; esac rc=$? exit $rcto
case $cOPT in 2) $CC $G -o $OUTF $OFILES -lf2c -lm;; esac rc=$? trap 0 exit $rc
overtake.o(.text+0x59): undefined reference to `MPI_COMM_WORLD' overtake.o(.text+0x81): undefined reference to `MPI_COMM_WORLD' ...
To fix this problem, you need a corrected f77 script. If you can edit
the script yourself, change the last 3 lines from
case $cOPT in 2) $CC $G -o $OUTF $OFILES -lf2c -lm;; esac rc=$? exit $rcto
case $cOPT in 2) $CC $G -o $OUTF $OFILES -lf2c -lm;; esac rc=$? trap 0 exit $rc