[mpich-discuss] configuring mpich 2 on Mac OS 10.6

[Brandt Belson]

Hello,
I'm trying to configure (then install) mpich 2 on a Mac OS 10.6, and I'm
having a problem. ./configure, without any additional options, fails. This
is probably an easy fix but I don't know what it is. I'm pasting the entire
output of configure below.

rainier:mpich2-1.2.1p1 bbelson$ ./configure
Configuring MPICH2 version 1.2.1p1
Running on system: Darwin rainier 10.2.0 Darwin Kernel Version 10.2.0: Tue
Nov  3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386
Executing mpich2prereq in
/home/bbelson/Downloads/mpich2-1.2.1p1/src/mpid/ch3 with
Executing mpich2prereq in
/home/bbelson/Downloads/mpich2-1.2.1p1/src/mpid/ch3/channels/nemesis
sourcing /home/bbelson/Downloads/mpich2-1.2.1p1/src/pm/mpd/mpich2prereq
sourcing /home/bbelson/Downloads/mpich2-1.2.1p1/src/pm/hydra/mpich2prereq
sourcing /home/bbelson/Downloads/mpich2-1.2.1p1/src/pm/gforker/mpich2prereq
sourcing /home/bbelson/Downloads/mpich2-1.2.1p1/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 ISO C89... none needed
checking how to run the C preprocessor... gcc -E
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 routines compiled with -O2 can be linked with ones compiled
without -O2... yes
checking for type of weak symbol alias support... no
checking whether __attribute__ ((weak)) allowed... yes
checking whether __attribute ((weak_import)) allowed... yes
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
checking whether Fortran 77 compiler accepts option -O2... yes
checking whether routines compiled with -O2 can be linked with ones compiled
without -O2... yes
checking how to get verbose linking output from gfortran... -v
checking for Fortran 77 libraries of gfortran...
 -L/usr/local/gfortran/lib/gcc/i386-apple-darwin8.10.1/4.5.0
-L/usr/local/gfortran/lib/gcc/i386-apple-darwin8.10.1/4.5.0/../../..
-lgfortran
checking whether gfortran accepts the FLIBS found by autoconf... yes
checking whether C can link with
 -L/usr/local/gfortran/lib/gcc/i386-apple-darwin8.10.1/4.5.0
-L/usr/local/gfortran/lib/gcc/i386-apple-darwin8.10.1/4.5.0/../../..
-lgfortran... yes
checking for linker for Fortran main programs... Use Fortran to link
programs
checking whether Fortran 77 and C objects are compatible... no
checking for file... file
configure: error: ****  Incompatible Fortran and C Object File Types!  ****
F77 Object File Type produced by "gfortran  -O2" is : : Mach-O object i386.
 C  Object File Type produced by "gcc  -O2" is : : Mach-O 64-bit object
x86_64.

Any help is appreciated, thank you!
Brandt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20100326/f7735a5c/attachment.htm>