dIt seems like this should be a simple problem. I am trying to get OpenMPI to compile on a CentOS 4.2 (like Redhat EL 4.2) box. It has installed gcc 3.4, and gcc 4.0. I want to compile OMPI with gcc4, but I am getting this error. What am I doing wrong?
[root@Cent01 openmpi-1.0.1]# CC=gcc4 CPP=gcc4 CXX=g++4 CXXCPP=g++4 F77=gfortran FC=gfortran ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes ============================================================================ == Configuring Open MPI ============================================================================ *** Checking versions checking Open MPI version... 1.0.1 checking Open MPI Subversion repository version... r8453 checking Open Run-Time Environment (ORTE) version... 1.0.1 checking ORTE Subversion repository version... r8453 checking Open Portable Access Layer (OPAL) version... 1.0.1 checking OPAL Subversion repository version... r8453 *** Initialization, setup configure: builddir: /root/Desktop/openmpi-1.0.1 configure: srcdir: /root/Desktop/openmpi-1.0.1 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for prefix by checking for ompi_clean... no installing to directory "/usr/local" *** Configuration options checking Whether to run code coverage... no checking whether to debug memory usage... no checking whether to profile memory usage... no checking if want developer-level compiler pickyness... no checking if want developer-level debugging code... no checking if want Fortran 77 bindings... yes checking if want Fortran 90 bindings... yes checking whether to enable PMPI... yes checking if want C++ bindings... yes checking if want to enable weak symbol support... yes checking if want run-time MPI parameter checking... runtime checking if want to install OMPI header files... no checking if want pretty-print stacktrace... yes checking if want deprecated executable names... no checking if want MPI-2 one-sided empty shell functions... no checking max supported array dimension in F90 MPI bindings... 4 checking if pty support should be enabled... yes checking if user wants dlopen support... yes checking if heterogeneous support should be enabled... yes checking if want trace file debugging... no ============================================================================ == Compiler and preprocessor tests ============================================================================ *** C compiler and preprocessor checking for style of include used by make... GNU checking for gcc... gcc4 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc4 accepts -g... yes checking for gcc4 option to accept ANSI C... none needed checking dependency style of gcc4... gcc3 checking whether gcc4 and cc understand -c and -o together... yes checking if compiler impersonates gcc... no checking if gcc4 supports -finline-functions... yes checking if gcc4 supports -fno-strict-aliasing... yes configure: WARNING: -fno-strict-aliasing has been added to CFLAGS checking for C optimization flags... -O3 -DNDEBUG -fno-strict-aliasing checking how to run the C preprocessor... gcc4 configure: error: C preprocessor "gcc4" fails sanity check See `config.log' for more details. [root@Cent01 openmpi-1.0.1]#
