Ralf,
Here's what I see:
$ objdump -p testmpi | grep NEEDED
NEEDED libutil.so.1
NEEDED libnsl.so.1
NEEDED libdl.so.2
NEEDED libbproc.so.4
NEEDED libpthread.so.0
NEEDED librt.so.1
NEEDED libm.so.6
NEEDED libc.so.6
Seems like mpicc is definitely linking in the pthread library.
Cheers,
Greg
On Mar 17, 2006, at 8:35 AM, Ralf Wildenhues wrote:
Hi Greg,
* Greg Watson wrote on Fri, Mar 17, 2006 at 04:17:27PM CET:
./configure --enable-static --disable-shared --without-threads --
with-
devel-headers
./configure --enable-static --disable-shared --without-threads --
without-mpi-threads --with-devel-headers
In both cases, I'm still seeing the thread library linked in the
final executable:
Likely I could not help you much with your problem, but:
$ mpicc -o testmpi testmpi.c
$ ldd testmpi
libutil.so.1 => /lib/libutil.so.1 (0x0f590000)
libnsl.so.1 => /lib/libnsl.so.1 (0x0e850000)
libdl.so.2 => /lib/libdl.so.2 (0x0fdc0000)
libbproc.so.4 => /usr/lib/libbproc.so.4 (0x0fe50000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x0fc40000)
librt.so.1 => /lib/tls/librt.so.1 (0x0f660000)
libm.so.6 => /lib/tls/libm.so.6 (0x30013000)
libc.so.6 => /lib/tls/libc.so.6 (0x0fe70000)
/lib/ld.so.1 => /lib/ld.so.1 (0x0ffd0000)
Please use "objdump -p testmpi | grep NEEDED" to find out whether
libpthread was linked in directly, or pulled in by one of the other
libraries (librt comes to mind).
Cheers,
Ralf
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
