On Oct 25, 2006, at 11:43 AM, Katherine Holcomb wrote:

...We support
multiple compilers (specifically PGI and Intel) and due to
incompatibilities in different vendors' f90 .mod files, we have separate
directories for OpenMPI with each compiler.  Therefore we cannot set a
global path to the OpenMPI binaries -- it will differ depending on the
user's choice of compiler. I have read about the --prefix flag and this does work, but our users are mostly barely conversant with Unix and many would have difficulty finding and specifying the appropriate path. (We use the modules software environment currently to set paths and the like
for them.)  Is there some way to specify something like "use the same
path as you are in" from the root process?  There was some allusion in
the FAQ to changing the wrappers to include directives, but the link led
to a "no such category" page.

I presume you left some critical piece of information out of your message, like the name and configuration of the batch queueing system you are using.

The answer to your question as worded may not be the best answer for your problem.

I have dealt with two cases similar to yours:

1) Large system using Modules and LSF batch queueing system -- this type of system requires the people configuring LSF to set up some stuff or the end users have to use --prefix flag to get the OpenMPI path, plus more to get the correct compiler (something I never figured out how to do before the LSF admins extended their LSF installation to cover OpenMPI). [what stuff I don't know, I'm not an LSF admin]

2) Local system I sysadm, learning Modules setup was going to take more time than I had available so I wrote a script that sets PATH, MANPATH, and LD_LIBRARY_PATH based on similar arguments as the real Module software (also G95_INCLUDE_PATH for g95). When the user sets the environmental variables via my script and then runs OpenMPI I see no problems with OpenMPI on the other nodes; however, we don't have a batch queuing system. I don't see why using the Modules software would be any different. One critical piece is that my script also aliases mpirun, for example "alias mpirun "mpirun --prefix /opt/g95/ openmpi/1.1.1 " (which the real modules software should also be able to do if needed) and I have only one installation of each type of compiler (g95, Intel, PGI, Absoft).

Michael

Reply via email to