On Feb 13, 2007, at 1:13 PM, David Gunter wrote:
We currently build 4 versions of Open-MPI for the various Fortran
compilers: gfortran, Intel, Pathscale and PGI.
We modify the build so that the compiler name is part of the rpm
filename. For the final install of the package we end up with the
following:
/opt/OpenMPI/openmpi-<version>-<compiler>/
Users software environments are controlled via the Module package,
thus a user will load her favorite flavor of compiler and Open-MPI
module at login or some other time and LD_LIBRARY_PATH and PATH,
etc, are set accordingly.
I second the modules package, we run 10 versions OMPI via modules.
http://modules.sourceforge.net/
Brock
-david
--
David Gunter
HPC-4: HPC Environments: Parallel Tools Team
Los Alamos National Laboratory
On Feb 13, 2007, at 10:03 AM, Steven A. DuChene wrote:
If we need to have a g95 version of openmpi and a second version
built with
intel compilers, how do others usually handle this? We would like
to do this
via rpms so we can easily push any changes out to the compute nodes
and try to eliminate any versioning problems. I was thinking a
different rpm name
and different locations and then users would have to adjust
environment
variables to use a particular build.
Is this how other sites have handled this?
Any suggestions or hists around this issue would be most appreciated.
--
Steve
_______________________________________________
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
