Re: [OMPI users] location of ompi libraries

2010-10-05 Thread Barrett, Brian W
David - You're correct - adding --enable-static (or it's file equivalent enable_static) causes components to be linked into libmpi instead of left as individual components. This is probably a bug, but it's what Open MPI's done for it's entire life, so it's unlikely to change. Removing the

Re: [OMPI users] location of ompi libraries

2010-10-05 Thread David Turner
Hi Jeff, Thanks for the response. Reviewing my builds, I realized that for 1.4.2, I had configured using contrib/platform/lanl/tlcc/optimized-nopanasas per Ralph Castain's suggestion. That file includes both: enable_dlopen=no enable_shared=yes enable_static=yes Here is my *real* issue. I

Re: [OMPI users] location of ompi libraries

2010-10-05 Thread Jeff Squyres
It is more than likely that you compiled Open MPI with --enable-static and/or --disable-dlopen. In this case, all of Open MPI's plugins are slurped up into the libraries themselves (e.g., libmpi.so or libmpi.a). That's why everything continues to work properly. On Oct 4, 2010, at 6:58 PM,

[OMPI users] location of ompi libraries

2010-10-04 Thread David Turner
Hi, In Open MPI 1.4.1, the directory lib/openmpi contains about 130 entries, including such things as mca_btl_openib.so. In my build of Open MPI 1.4.2, lib/openmpi contains exactly three items: libompi_dbg_msgq.a libompi_dbg_msgq.la libompi_dbg_msgq.so I have searched my 1.4.2 installation