Ah ha! I didn't know that option was available as I didn't see it in the documentation or in ./configure --help.
I just ended up rebuilding and installing torque to my /opt/torque share. Thank you for your help with this. Matt ______________________________ 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 Brian Barrett Sent: Friday, June 08, 2007 3:15 PM To: Open MPI Users Subject: Re: [OMPI users] v1.2.2 mca base unable to open pls/ras tm Or tell Open MPI not to build torque support, which can be done at configure time with the --without-tm option. Open MPI tries to build support for whatever it finds in the default search paths, plus whatever things you specify the location of. Most of the time, this is what the user wants. In this case, however, it's not what you wanted so you'll have to add the --without-tm option. Hope this helps, Brian On Jun 8, 2007, at 1:08 PM, Cupp, Matthew R wrote: > 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-bounces@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 > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users _______________________________________________ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
