Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

From: Brock Palen (brockp_at_[hidden])
Date: 2007-02-13 13:27:23

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.


> -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
>> users_at_[hidden]
> _______________________________________________
> users mailing list
> users_at_[hidden]