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.   **
> **************************************************************
> ***************
> 
> 

Reply via email to