Problems configuring


Up: Problems Next: General Previous: Submitting bug reports



Up: Problems Next: General Previous: Submitting bug reports


General


Up: Problems configuring Next: LINUX Previous: Problems configuring

    1.


    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 me 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:

      1. In configure, change trap 'rm -f confdefs*' 0 to trap 'rm -f confdefs*' 1
      2. After configure finishes, remove the file confdefs.h manually.

    3. Q: configure reports errors of the form
    checking gnumake... 1: Bad file number 
    
    A: Some versions of the bash shell do not handle output redirection correctly. Either upgrade your version of bash or run configure under another shell (such as /bin/sh). Make sure that the version of sh that you use is not an alias for bash. configure trys to detect this situation and will normally issue an error message.


    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.



Up: Problems configuring Next: LINUX Previous: Problems configuring


LINUX


Up: Problems configuring Next: Problems building  mpich Previous: General

    1.
    2.



Up: Problems configuring Next: Problems building  mpich Previous: General