Davide probably has it. Adding -lpthread should help address this.
As another suggestion, There is a known issue in LAM/MPI 7.1.1 with
regard to intel compilers that can cause LAM to hang. This was
addressed in the latest beta series, so you could also try upgrading
to the latest LAM beta:
http://www.lam-mpi.org/beta/
On Feb 28, 2006, at 3:23 AM, Davide Cesari wrote:
> Robert LeBlanc ha scritto:
>> I've been trying to compile Charmm for three weeks now and just
>> can't figure
>> out how to resolve this error. When the final binary is being
>> assemblied I
>> get tons of messages like this:
>>
>> /usr/local/lam/intel_80/lib/libmpi.a(malloc.o)(.text+0xa): In
>> function
>> `malloc_atfork':
>> : undefined reference to `pthread_getspecific'
>> /usr/local/lam/intel_80/lib/libmpi.a(malloc.o)(.text+0x15e): In
>> function
>> `free_atfork':
>> : undefined reference to `pthread_getspecific'
>> /usr/local/lam/intel_80/lib/libmpi.a(malloc.o)(.text+0x22d): In
>> function
>> `ptmalloc_lock_all':
>> : undefined reference to `pthread_getspecific'
>> /usr/local/lam/intel_80/lib/libmpi.a(malloc.o)(.text+0x23f): In
>> function
>> `ptmalloc_lock_all':
>> : undefined reference to `pthread_setspecific'
>> /usr/local/lam/intel_80/lib/libmpi.a(malloc.o)(.text+0x261): In
>> function
>> `ptmalloc_unlock_all':
>
> Probably adding -lpthread to the linking command line helps, at
> least to step
> forward to the next error message, pthread_get/setspecific appear
> to be in
> libpthread.
> Davide
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
----
Josh Hursey
jjhursey_at_[hidden]
http://www.lam-mpi.org/
|
