This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
So I either have to uninstall torque, make the shared libraries
available on all nodes, or have torque as static libraries on the head
Battelle Memorial Institute
Statistics and Information Analysis
From: users-bounces_at_[hidden] [mailto:users-bounces_at_[hidden]] 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
> 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.
users mailing list