[mpich-discuss] Getting MPICH2 to find/use g95 fortran

[Rajeev Thakur]

You need to put them all on one line:
 
# $ F77=/path/to/g95 F90=/path/to/g95 ./configure
--prefix=/some/place/mpich2-install
 
 

  _____  

From: owner-mpich-discuss at mcs.anl.gov
[mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of PattiMichelle
Sent: Tuesday, May 13, 2008 10:02 PM
To: mpich-discuss at mcs.anl.gov
Subject: Re: [mpich-discuss] Getting MPICH2 to find/use g95 fortran


Pavan Balaji wrote: 


You can force MPICH2 to use g95 by setting environment variables at
configure time: 

  $ F77=/path/to/g95 F90=/path/to/g95 ./configure
--prefix=/some/place/mpich2-install 

  $ make && make install 

 -- Pavan 


I didn't have luck with this:patti-desktop:
# F77=/usr/local/bin/g95
# F90=/usr/local/bin/g95
# ./configure
Configuring MPICH2 version 1.0.7
Running on system: Linux patti-desktop 2.6.18.8-0.9-default #1 SMP Sun Feb
10 22:48:05 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux
Executing mpich2prereq in /usr/local/mpich2-1.0.7/src/mpid/ch3 with
Executing mpich2prereq in /usr/local/mpich2-1.0.7/src/mpid/ch3/channels/sock
sourcing /usr/local/mpich2-1.0.7/src/pm/mpd/mpich2prereq
sourcing /usr/local/mpich2-1.0.7/src/pm/mpd/setup_pm
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking whether C compiler accepts option -O2... yes
checking whether routines compiled with -O2 can be linked with ones compiled
without -O2... yes
checking for type of weak symbol support... pragma weak
checking whether __attribute__ ((weak)) allowed... yes
checking for multiple weak symbol support... yes
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... no
checking whether gfortran accepts -g... no
checking whether Fortran 77 compiler accepts option -O2... no
checking how to get verbose linking output from gfortran... configure:
WARNING: compilation failed

checking for Fortran libraries of gfortran...
checking whether gfortran accepts the FLIBS found by autoconf... no
checking for valid entries in FLIBS...
checking whether C can link with ... yes
checking for linker for Fortran main programs... configure: error: Could not
compile Fortran test program



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20080513/1f4aba4c/attachment.htm>