livelfs wrote: > > your 1.2.1 build error seems to be the one I bumped into. > Try to avoid to give an absolute path to CC macro when you run configure > (check the archives)
Hmmm, to get a decent fortran compiler for my AlphaServers, I have to compile my own GCC compiler set (the default with CentOS is not good enough). Hence, I have gcc/g++/gfortran both in /opt/gcc/bin and /usr/bin. I'd like to set CC=/opt/gcc/bin/gcc, FC=/opt/gcc/bin/gfortran etc. However, instead I must do CC=gcc, FC=gfortran and manually let the path point to /opt/gcc/bin such that it first searches in /opt/gcc/bin. However, by default /opt/gcc/bin is not in my PATH, because in general I'd like to use the original GCC compiler set that comes with the OS. Then, what happens when I compile my MPI code "mpif90 mycode.f90"? Does OpenMPI remember to use the compilers in /opt/gcc/bin, or will it then erroneously use the ones in /usr/bin ? Even better: is there a patch available to fix this in the 1.2.1 tarball, so that I can set the full path again with CC? (is it only the CC macro, or also F77, F90, CXX, CPP and CXXCPP?) Thanks, Rob. --------------------------------- Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
