[mpich-discuss] Problem building MPICH2 with shared lib on Mac OS10.5.5

[Rajeev Thakur]

It is possible that by default your C compiler creates 64-bit binaries
whereas Fortran compiler creates 32-bit binaries, or vice-versa. If you are
using gcc, try setting CFLAGS to -m32 before running configure. If that
doesn't work, try setting CFLAGS to -m64. 

Rajeev

> -----Original Message-----
> From: mpich-discuss-bounces at mcs.anl.gov 
> [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of 
> Blanchette, Marco
> Sent: Sunday, February 01, 2009 4:29 PM
> To: mpich-discuss at mcs.anl.gov
> Subject: [mpich-discuss] Problem building MPICH2 with shared 
> lib on Mac OS10.5.5
> 
> Dear MPICH2 users,
> 
> I have been trying to build MPICH2 1.0.8 under Mac OS 10.5.5 
> with shared libraries. The shared libraries are required to 
> build the R module Rmpi that allows us to run R in parallel 
> across our cluster. However, I have been having a lot of 
> trouble to get the Rmpi package built correctly and I am 
> trying to investigate whether the problem boils down 
> something going wrong while building MPICH2.
> 
> I have gcc installed as well as gfortran. I gave up for the 
> moment to try building a 64-bit MPICH2 as the make process 
> was breaking down at multiple places.
> 
> Right now I have been trying to get a 32-bit mpich2 deployed 
> on my workstation and try to build Rmpi in 32-bit (a 64-bit 
> will be require later...).
> 
> When I build MPICH2 following configuration with './configure 
> --enable-sharedlibs=gcc-osx', MPICH2 build correctly and 
> seems to run fine. However, I get the following error during 
> the build process:
> 
> ad_fstype.c: In function 'ADIO_FileSysType_fncall':
> ad_fstype.c:383: warning: comparison is always false due to 
> limited range of data type
> ad_fstype.c: In function 'ADIO_FileSysType_fncall':
> ad_fstype.c:383: warning: comparison is always false due to 
> limited range of data type
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.la(osserv.lo) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.la(osserv.lo) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.la(osserv.lo) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: libmpichf90.a(mpi_base.o) has no symbols
> ranlib: file: libmpichf90.a(mpi_base.o) has no symbols
> ranlib: file: ../../../lib/libmpich.la(osserv.lo) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.la(osserv.lo) has no symbols
> 
> Then, if I try to build the R package, I get an error related 
> to the inability of the package to load the shared library.
> 
> Building MPICH2 without shared libraries following the 
> default ./configure setting give the following errors
> 
> ad_fstype.c: In function 'ADIO_FileSysType_fncall':
> ad_fstype.c:383: warning: comparison is always false due to 
> limited range of data type
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: libmpichf90.a(mpi_base.o) has no symbols
> ranlib: file: libmpichf90.a(mpi_base.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> ranlib: file: ../../../lib/libmpich.a(osserv.o) has no symbols
> 
> Are these bugs that prevent me from building the R module on 
> the shared library or simple warnings that can be ignore?
> 
> Also, is there anyone that has successfully build a 64-bit 
> MPICH2 with fortran support under Mac OS 10.5.5? Would you 
> mind sharing your successful configuration setup?
> 
> Thanks for your help.
> 
> --
> Marco Blanchette, Ph.D.
> Assistant Investigator
> Stowers Institute for Medical Research
> 1000 East 50th St.
> 
> Kansas City, MO 64110
> 
> Tel: 816-926-4071
> Cell: 816-726-8419
> Fax: 816-926-2018
>