I guess you are not particularly interested on Modules or LMod either.
You probably don't administer this cluster,
but are just trying to have MPI working, right?
Are you trying to use Open MPI or MPICH?
Your email mentions both.
Let's assume it is Open MPI.
Is recompiling your code with the new version of Open MPI installed
in the cluster an option for you, or not?
If it is, that may be the simplest and best solution.
If the cluster has a system administrator, you may ask him about
the best way to set up your environment variables.
In any case, for your Open MPI to work you need your PATH and
LD_LIBRARY_PATH to be correctly set.
If the system administator migrated OpenMPI 1.4.4 to a "retired"
directory, you may need to adjust PATH and LD_LIBRARY_PATH
to point to the "retired" directories (if they are still functional).
may show what you have.
Does the cluster use modules, perhaps?
What do you get from
As a workaround you're using bash, you could add these to .bashrc
if csh to .cshrc
setenv PATH /opt/apps/openmpi/retired/1.4.4-intel/bin:$PATH
I hope this helps,
On 05/16/2014 05:39 PM, Ben Lash wrote:
> My cluster has just upgraded to a new version of MPI, and I'm using an
> old one. It seems that I'm having trouble compiling due to the compiler
> wrapper file moving (full error here: http://pastebin.com/EmwRvCd9)
> "Cannot open configuration file
> I've found the file on the cluster at
> How do I tell the old mpi wrapper where this file is?
> I've already corrected one link to mpich ->
> /opt/apps/openmpi/retired/1.4.4-intel/, which is in the software I'm
> trying to recompile's lib folder
> (/home/bl10/CMAQv5.0.1/lib/x86_64/ifort). Thanks for any ideas. I also
> tried changing $pkgdatadir based on what I read here:
> --Ben L
> users mailing list