I'm not able to exactly duplicate your issue. I ran into something
very similar, but according to the output of laminfo, it shouldn't
have caused problems for you. Can you send me the output of:
mpif77 -o a.out a_mpi_source.o -showme
as well as the output from running nm on liblamf77mpi.a and libmpi.a
for your installation? The last two are going to be really big, so
please compress before sending.
Thanks,
Brian
On Nov 9, 2005, at 12:09 PM, ERiC LICHAMYON wrote:
> Sorry, i'm a little newbie :p
> here what you asked.
>
> Thank you for your help :)
>
>
> LAM/MPI: 7.1.2b27
> Prefix: /usr/local
> Architecture: powerpc-apple-darwin8.3.0
> Configured by: eric
> Configured on: Tue Nov 8 21:24:04 CET 2005
> Configure host: ERiC.local
> Memory manager: darwin7malloc
> C bindings: yes
> C++ bindings: yes
> Fortran bindings: yes
> C compiler: gcc
> C++ compiler: g++
> Fortran compiler: g95
> Fortran symbols: double_underscore
> C profiling: yes
> C++ profiling: yes
> Fortran profiling: yes
> C++ exceptions: no
> Thread support: yes
> ROMIO support: yes
> IMPI support: no
> Debug support: no
> Purify clean: no
> SSI boot: globus (API v1.1, Module v0.6)
> SSI boot: rsh (API v1.1, Module v1.1)
> SSI boot: slurm (API v1.1, Module v1.0)
> SSI coll: lam_basic (API v1.1, Module v7.1)
> SSI coll: shmem (API v1.1, Module v1.0)
> SSI coll: smp (API v1.1, Module v1.2)
> SSI rpi: crtcp (API v1.1, Module v1.1)
> SSI rpi: lamd (API v1.0, Module v7.1)
> SSI rpi: sysv (API v1.0, Module v7.1)
> SSI rpi: tcp (API v1.0, Module v7.1)
> SSI rpi: usysv (API v1.0, Module v7.1)
> SSI cr: self (API v1.0, Module v1.0)
> <config.log>
>
> Le 9 nov. 05 à 17:51, Brian Barrett a écrit :
>
>> On Nov 8, 2005, at 4:51 PM, ERiC LICHAMYON wrote:
>>
>>> Hello,
>>> I installed lam/mpi with g95 as fortran compiler on Mac OS X 10.4.3.
>>> In order to do so, I ran successively :
>>> ./configure FC=g95 --prefix=/usr/local
>>> ./make
>>> ./make install
>>>
>>> The compilation succeeded, meaning without premature errors.
>>>
>>> Once installed, i wanted to test it, so I did :
>>> mpif77 -c a_mpi_source.f90 //which compile without errors
>>>
>>> and then
>>>
>>> mpif77 -o a.out a_mpi_source.o
>>>
>>> and the errors occur at that moment, with this output :
>>> ld: Undefined symbols:
>>> _mpi_comm_null_copy_fn__
>>> _mpi_comm_null_delete_fn__
>>> _mpi_null_copy_fn__
>>> _mpi_null_delete_fn__
>>> _mpi_type_null_copy_fn__
>>> _mpi_type_null_delete_fn__
>>> _mpi_win_null_copy_fn__
>>> _mpi_win_null_delete_fn__
>>> _pmpi_wtick__
>>> _pmpi_wtime__
>>>
>>> I'd be grateful if somebody could help me with this :-)
>>
>> Can you please send the output of laminfo and the config.log from
>> building LAM? It's not really possible to tell what went wrong from
>> the information you included.
>>
>> Thanks,
>>
>> Brian
>>
>>
>> --
>> Brian Barrett
>> LAM/MPI developer and all around nice guy
>> Have a LAM/MPI day: http://www.lam-mpi.org/
>>
>>
>> _______________________________________________
>> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|