So I either have to uninstall torque, make the shared libraries available on all nodes, or have torque as static libraries on the head node?
______________________________ Matt Cupp Battelle Memorial Institute Statistics and Information Analysis -----Original Message----- From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On Behalf Of Jeff Squyres Sent: Friday, June 08, 2007 2:21 PM To: Open MPI Users Subject: Re: [OMPI users] v1.2.2 mca base unable to open pls/ras tm On Jun 8, 2007, at 2:06 PM, Cupp, Matthew R wrote: > Yes. But the /opt/torque directory is just the source, not the actual > installed directory. The actual installed directory on the head > node is > the default location of /usr/lib/something. And that is not > accessable > by every node. > > But should it matter if it's not accessable if I don't specify > --with-tm? I was wondering if ./configure detects torque has been > installed, and then builds the associated components under the > assumption that it's available. This is what OMPI does. However, if you only have static libraries for Torque, the issue should be moot -- the relevant bits should be statically linked into the OMPI tm plugins. But if your Torque libraries are shared, then you do need to have them available on all nodes for OMPI to be able to leverage native Torque/TM support. Make sense? -- Jeff Squyres Cisco Systems _______________________________________________ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
