Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Why compilig in global paths (only) for configuretion files?
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-09-15 14:15:59


On Sep 15, 2008, at 11:22 AM, Paul Kapinos wrote:

> But the setting of the environtemt variable OPAL_PREFIX to an
> appropriate value (assuming PATH and LD_LIBRARY_PATH are setted too)
> is not enough to let the OpenMPI rock&roll from the new lokation.

Hmm. It should be.

> Because of the fact, that all the files containing settings for
> opal_wrapper, which are located in share/openmpi/ and called e.g.
> mpif77-wrapper-data.txt, contain (defined by installation with --
> prefix) hard-coded paths, too.

Hmm; they should not. In my 1.2.7 install, I see the following:

-----
[11:14] svbu-mpi:/home/jsquyres/bogus/share/openmpi % cat mpif77-
wrapper-data.txt
# There can be multiple blocks of configuration data, chosen by
# compiler flags (using the compiler_args key to chose which block
# should be activated. This can be useful for multilib builds. See the
# multilib page at:
# https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264
# for more information.

project=Open MPI
project_short=OMPI
version=1.2.7rc6r19546
language=Fortran 77
compiler_env=F77
compiler_flags_env=FFLAGS
compiler=gfortran
extra_includes=
preprocessor_flags=
compiler_flags=
linker_flags=
libs=-lmpi_f77 -lmpi -lopen-rte -lopen-pal -ldl -Wl,--export-
dynamic -lnsl -lutil -lm -ldl
required_file=not supported
includedir=${includedir}
libdir=${libdir}
[11:14] svbu-mpi:/home/jsquyres/bogus/share/openmpi %
-----

Note the "includedir" and "libdir" lines -- they're expressed in terms
of ${foo}, which we can replace when OPAL_PREFIX (or related) is used.

What version of OMPI are you using?

-- 
Jeff Squyres
Cisco Systems