The problems are related to the bindings. I run nm against the libraries and it clearly shows that, among all different aliases used, the ones used by the compiler are not there.
For example, for the FORTAN function called MPI_COMM_RANK, this is what is defined in the libraries: .MPI_Comm_rank .PMPI_Comm_rank MPI_Comm_rank PMPI_Comm_rank .mpi_comm_rank__ .mpi_comm_rank_f MPI_COMM_RANK PMPI_COMM_RANK mpi_comm_rank mpi_comm_rank_ mpi_comm_rank__ mpi_comm_rank_f pmpi_comm_rank pmpi_comm_rank_ pmpi_comm_rank__ As I previously wrote, the one needed is: .mpi_comm_rank And it is not in the list Note that .mpi_comm_rank__ is defined, so, in the mean time, in the FORTRAN code, if I use MPI_COMM_RANK__ instead of MPI_COMM_RANK, it works ... but this is a temporary fix. Sergio -----Original Message----- From: Jeff Squyres (jsquyres) [mailto:jsquy...@cisco.com] Sent: Monday, May 01, 2006 9:10 PM To: Open MPI Users Subject: Re: [OMPI users] F77 in AIX Can you run "mpif77 --showme"? This will show the underlying command that mpif77 is issuing. We can verify that it is linking against the right Open MPI libraries, etc. > -----Original Message----- > From: users-boun...@open-mpi.org > [mailto:users-boun...@open-mpi.org] On Behalf Of Brignone, Sergio > Sent: Monday, May 01, 2006 2:14 PM > To: us...@open-mpi.org > Subject: [OMPI users] F77 in AIX > > Hi, > > I tried to compile a FORTRAN 77 test case and it failed when linking: > > %>mpif77 -o fpi fpi.f > "/usr/local/include/mpif.h", line 64.38: 1515-009 (E) Null literal > string is not permitted. A single blank is assumed. > ** main === End of Compilation 1 === > 1501-510 Compilation successful for file fpi.f. > ld: 0711-317 ERROR: Undefined symbol: .mpi_init > ld: 0711-317 ERROR: Undefined symbol: .mpi_comm_rank > ld: 0711-317 ERROR: Undefined symbol: .mpi_comm_size > ld: 0711-317 ERROR: Undefined symbol: .mpi_bcast > ld: 0711-317 ERROR: Undefined symbol: .mpi_reduce > ld: 0711-317 ERROR: Undefined symbol: .mpi_finalize > ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more > information. > > > Do you know how should I define the bindings to avoid this kind of > problems? > > Thanks > > Sergio > > > ************************************************************** > *************** > ** > ** > ** WARNING: This email contains an attachment of a very > suspicious type. ** > ** You are urged NOT to open this attachment unless you are > absolutely ** > ** sure it is legitmate. Opening this attachment may cause > irreparable ** > ** damage to your computer and your files. If you have any > questions ** > ** about the validity of this message, PLEASE SEEK HELP > BEFORE OPENING IT. ** > ** > ** > ** This warning was added by the IU Computer Science Dept. > mail scanner. ** > ************************************************************** > *************** > >
