[mpich-discuss] MPICH2 on Mac OS x86-64

Dorian Krause dorian at uni-bonn.de
Mon Jun 1 11:20:45 CDT 2009


You need to add CFLAGS=-m64 CCFLAGS=-64 CXXFLAGS=-m64 F77FLAGS=-m64 
F90FLAGS=-m64 ...

try ./configure --help to find out the flags for the various compiler

Hope this helps,
Dorian


Dmitry Nedospasov wrote:
> Okay I'm assuming the -m64 CFLAGS is what I wanted, so thanks for 
> that, but now i get the error that my fortran compiler is incompatibel 
> with my GCC
>
> Thanks,
>
> D.
>
> $ export CFLAGS=-m64; ./configure --prefix=/Users/russo/build/mpich2 
> --enable-sharedlibs=osx-gcc
> Configuring MPICH2 version 1.1rc1 with 
>  '--prefix=/Users/russo/build/mpich2' '--enable-sharedlibs=osx-gcc' 
> 'CFLAGS=-m64'
> Running on system: Darwin kovalchuk.nedos.net 9.7.0 Darwin Kernel 
> Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; 
> root:xnu-1228.12.14~1/RELEASE_I386 i386
> Executing mpich2prereq in 
> /Users/russo/build/mpich2-1.1rc1/src/mpid/ch3 with 
> Executing mpich2prereq in 
> /Users/russo/build/mpich2-1.1rc1/src/mpid/ch3/channels/nemesis
> sourcing /Users/russo/build/mpich2-1.1rc1/src/pm/mpd/mpich2prereq
> sourcing /Users/russo/build/mpich2-1.1rc1/src/pm/hydra/mpich2prereq
> sourcing /Users/russo/build/mpich2-1.1rc1/src/pm/gforker/mpich2prereq
> sourcing /Users/russo/build/mpich2-1.1rc1/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... no
> checking for g95... g95
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g95 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 g95... -v
> checking for Fortran 77 libraries of g95... 
>  -L/opt/local/bin/../lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/ 
> -L/opt/local/bin/../lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4 
> -L/opt/local/lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/ 
> -L/usr/lib/gcc// 
> -L/opt/local/bin/../lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/// 
> -L/opt/local/lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/// -L/usr/lib// 
> -lf95 -lm -lSystemStubs -lmx
> checking whether g95 accepts the FLIBS found by autoconf... yes
> checking whether C can link with 
>  -L/opt/local/bin/../lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/ 
> -L/opt/local/bin/../lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4 
> -L/opt/local/lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/ 
> -L/usr/lib/gcc// 
> -L/opt/local/bin/../lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/// 
> -L/opt/local/lib/gcc-lib/i386-apple-darwin9.6.0/4.0.4/// -L/usr/lib// 
> -lf95 -lm -lSystemStubs -lmx... 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 "g95  -O2" is : : Mach-O object i386.
>  C  Object File Type produced by "gcc -m64 -O2" is : : Mach-O 64-bit 
> object x86_64.
>
>
> On Jun 1, 2009, at 17:30 , Rajeev Thakur wrote:
>
>> Please send us the output of configure and make (the output printed on
>> the screen).
>>
>> Rajeev
>>
>>> -----Original Message-----
>>> From: mpich-discuss-bounces at mcs.anl.gov 
>>> <mailto:mpich-discuss-bounces at mcs.anl.gov>
>>> [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of
>>> Dmitry Nedospasov
>>> Sent: Monday, June 01, 2009 6:00 AM
>>> To: mpich-discuss at mcs.anl.gov <mailto:mpich-discuss at mcs.anl.gov>
>>> Subject: [mpich-discuss] MPICH2 on Mac OS x86-64
>>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Hello,
>>>
>>> I'm trying to compile MPICH2 for Mac OS, but the subsequent
>>> mpi programs that i compile, complain that:
>>>
>>> ld warning: in /opt/local/lib/libcrypto.dylib, file is not of
>>> required architecture
>>>
>>> I was curious is there a way to force the architecture to be
>>> Mac OS x86-64?
>>>
>>> Thanks,
>>>
>>> Dmitry
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.9 (Darwin)
>>>
>>> iEYEARECAAYFAkojtJsACgkQdm82SADo56rOQwCeLA6ZZ6BgiSQhHaKpQH/lLeNT
>>> 4cMAnjj93Tte6yfuMYXKc2ebGD96z2Ii
>>> =VyjT
>>> -----END PGP SIGNATURE-----
>>>
>>
>



More information about the mpich-discuss mailing list