[mvapich-discuss] Errors on Fedora 13

[Jonathan Perkins]

Vladmir:
Pavan's information is correct.  Regarding the build failure with
mvapich2-1.5.  Are you seeing the following error?

AR cr libmpiexec.a cmnargs.o process.o ioloop.o pmiserv.o labelout.o
env.o newsession.o rm.o pmiport.o dbgiface.o
 RANLIB          libmpiexec.a
make[4]: Leaving directory `/home/jonathan/mvapich2-1.5/src/pm/util'
gcc -g -O2 -DNDEBUG -O2    -o mpiexec mpiexec.o  \
       ../util/libmpiexec.a ../../../lib/libmpich.a -lpthread -lrdmacm
-libverbs -libumad    -lrt
/usr/bin/ld: ../../../lib/libmpich.a(mem_hooks.o): undefined reference
to symbol 'dlsym@@GLIBC_2.2.5'
/usr/bin/ld: note: 'dlsym@@GLIBC_2.2.5' is defined in DSO
/lib64/libdl.so.2 so try adding it to the linker command line
/lib64/libdl.so.2: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [mpiexec] Error 1
make[3]: Leaving directory `/home/jonathan/mvapich2-1.5/src/pm/gforker'
make[2]: *** [all-redirect] Error 1
make[2]: Leaving directory `/home/jonathan/mvapich2-1.5/src/pm'
make[1]: *** [all-redirect] Error 2
make[1]: Leaving directory `/home/jonathan/mvapich2-1.5/src'
make: *** [all-redirect] Error 2

If so, it looks like this issue is that discussed in
http://fedoraproject.org/wiki/UnderstandingDSOLinkChange.  I found
that specifying LDFLAGS='-ldl' can be used as a workaround for this
issue.

ex: ./configure --prefix=/path/to/install LDFLAGS='-ldl'

I'd like to suggest trying this work around with mvapich2-1.5 or using
mvapich2-1.4.1 which contains several bug fixes and other enhancements
compared to mvapich2-1.4.

On Tue, Jul 27, 2010 at 6:17 PM, Pavan Balaji <balaji at mcs.anl.gov> wrote:
>
> These are leaks in memory and other handles allocated within the MPI library. When you provide the --enable-dbg=mem,meminit options, these are kept track of within the library and reported at Finalize time. While annoying, they are relatively harmless. The program shouldn't fail because of this.
>
>  -- Pavan
>
> --
> Pavan Balaji
> http://www.mcs.anl.gov/~balaji
>
> ----- "Vladimir Florinski" <vaf0001 at uah.edu> wrote:
>
>> We are having problems with mvapich on Fedora 13. The version is 1.4
>> (1.5 had many build problems, so we gave up on that). With 1.4, a
>> simplest code consisting of only MPI_Init and MPI_Finalize fails like
>> this:
>>
>> ./a.out
>> [0] 24 at [0x000000000174e498], mpid_vc.c[79]
>> [0] 24 at [0x000000000174e3d8], mpid_vc.c[79]
>> [0] 16 at [0x000000000174e268], grouputil.c[58]
>> [0] 16 at [0x000000000174e1a8], grouputil.c[58]
>> [0] 8 at [0x000000000174e0f8], create_2level_comm.c[139]
>> [0] 8 at [0x000000000174df98], create_2level_comm.c[118]
>> [0] 8 at [0x000000000174dee8], ch3_smp_progress.c[1166]
>> [0] 8 at [0x000000000174de38], ch3_smp_progress.c[1164]
>> [0] 8 at [0x000000000174dd88], ch3_smp_progress.c[1162]
>> [0] 336 at [0x000000000174da08], ch3_shmem_coll.c[105]
>> [0] 1432 at [0x0000000001747298], ch3_init.c[246]
>>
>> (this is produced by MPI_Finalize)
>>
>> Here is the output of mpiname:
>>
>> MVAPICH2 1.4.0 2009-10-29 ch3:mrail
>>
>> Compilation
>> CC: gcc -m64 -O3 -fno-strict-aliasing -g
>> CXX: g++ -m64 -O3 -g
>> F77: gfortran -m64  -g
>> F90: gfortran -m64  -g
>>
>> Configuration
>> --prefix=/usr/lib64/mvapich2/1.4-gcc
>> --mandir=/usr/lib64/mvapich2/1.4-gcc/man
>> --enable-error-checking=runtime
>> --enable-timing=none --enable-g=mem,dbg,meminit --enable-mpe
>> --enable-sharedlibs=gcc --with-rdma=gen2
>>
>> Any ideas for what could be wrong?
>>
>>
>> --
>> Vladimir Florinski <vaf0001 at uah.edu>
>>
>> _______________________________________________
>> mvapich-discuss mailing list
>> mvapich-discuss at cse.ohio-state.edu
>> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>
>



-- 
Jonathan Perkins