[mpich-discuss] Could not determine a way to link a Fortran test program!

[Anthony Chan]

Could you send us the the top-level config.log generated (automatically) by configure ?

A.Chan


----- Original Message -----
> Hi,
> 
> I am running into a very irritating problem compiling mpich to use the
> intel fortran and c/c++ compilers. It always errors out in the
> ./configure phase
> 
> I've ran the following commands:
> source /sayre/intel/11.1/bin/iccvars.sh intel64
> source /sayre/intel/11.1/bin/ifortvars.sh intel64
> ./configure --prefix=/sayre --enable-f77 --enable-fc --enable-cxx
> --enable-mpe CC=/sayre/bin/icc CXX=/sayre/bin/icpc FC=/sayre/bin/ifort
> F77=/sayre/bin/ifort |& tee configure.log
> 
> with ifort and icc located at /sayre/intel/11.1/bin/intel64/ (I made a
> symlink to /sayre/bin to make things easier for me. This is intended
> to be a shared repository for commonly used software.
> 
> It fails with:
> 
> config.status: creating src/opa_config.h - prefix OPA for src/config.h
> defines
> config.status: src/opa_config.h is unchanged
> configure: ===== done with src/openpa configure =====
> sourcing /sayre/temp/mpich2-1.4/src/pm/hydra/mpich2prereq
> checking whether the compiler defines __func__... yes
> checking whether the compiler defines __FUNC__... no
> checking whether the compiler sets __FUNCTION__... yes
> checking whether C compiler accepts option -O2... yes
> checking whether C compiler option -O2 works with an invalid prototype
> program... yes
> checking whether routines compiled with -O2 can be linked with ones
> compiled without -O2... yes
> checking for type of weak symbol alias support... pragma weak
> checking whether __attribute__ ((weak)) allowed... yes
> checking whether __attribute__ ((weak_import)) allowed... yes
> checking whether __attribute__((weak,alias(...))) allowed... no
> checking for multiple weak symbol support... yes
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether /sayre/bin/ifort accepts -g... yes
> checking whether Fortran 77 compiler accepts option -O2... no
> checking how to get verbose linking output from /sayre/bin/ifort... -v
> checking for Fortran 77 libraries of /sayre/bin/ifort...
> -L/sayre/intel/11.1/lib/intel64 -L/sayre/intel/11.1/ipp/em64t/lib
> -L/sayre/intel/11.1/mkl/lib/em64t
> -L/sayre/intel/11.1/tbb/em64t/cc4.1.0_libc2.4_kernel2.6.16.21/lib
> -L/lib -L/usr/lib/gcc/x86_64-redhat-linux/4.6.0
> -L/usr/lib/gcc/x86_64-redhat-linux/4.6.0/../../../../lib64
> -L/lib/../lib64 -L/usr/lib/../lib64
> -L/usr/lib/gcc/x86_64-redhat-linux/4.6.0/../../.. -L/lib64
> -L/usr/lib64 -L/usr/lib -lifport -lifcore -limf -lsvml -lm -lipgo
> -lirc -lpthread -lirc_s -ldl
> checking whether /sayre/bin/ifort accepts the FLIBS found by
> autoconf... no
> checking for valid entries in FLIBS...
> checking whether /sayre/bin/icc links with FLIBS found by autoconf...
> yes
> checking whether Fortran 77 and C objects are compatible... no
> checking for file... file
> checking for linker for Fortran main program... configure: error:
> Could not determine a way to link a Fortran test program!
> 
> 
> Any idea what this is caused by, or how to fix it?
> 
> Thank you,
> Chris
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss