Open MPI logo

Open MPI User's Mailing List Archives

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

From: Anthony Chan (chan_at_[hidden])
Date: 2007-02-15 19:51:01


As long as mpicc is working, try configuring mpptest as

mpptest/configure MPICC=<OpenMPI-install-dir>/bin/mpicc

or

mpptest/configure --with-mpich=<OpenMPI-install-dir>

A.Chan

On Thu, 15 Feb 2007, Eric Thibodeau wrote:

> Hi Jeff,
>
> Thanks for your response, I eventually figured it out, here is the
> only way I got mpptest to compile:
>
> export LD_LIBRARY_PATH="$HOME/openmpi_`uname -m`/lib"
> CC="$HOME/openmpi_`uname -m`/bin/mpicc" ./configure --with-mpi="$HOME/openmpi_`uname -m`"
>
> And, yes I know I should use the mpicc wrapper and all (I do RTFM :P ) but
> mpptest is less than cooperative and hasn't been updated lately AFAIK.
>
> I'll keep you posted on some results as I get some results out (testing
> TCP/IP as well as the HyperTransport on a Tyan Beast). Up to now, LAM-MPI
> seems less efficient at async communications and shows no improovments
> with persistant communications under TCP/IP. OpenMPI, on the other hand,
> seems more efficient using persistant communications when in a
> HyperTransport (shmem) environment... I know I am crossing many test
> boudaries but I will post some PNGs of my results (as well as how I got to
> them ;)
>
> Eric
>
> On Thu, 15 Feb 2007, Jeff Squyres wrote:
>
> > I think you want to add $HOME/openmpi_`uname -m`/lib to your
> > LD_LIBRARY_PATH. This should allow executables created by mpicc (or
> > any derivation thereof, such as extracting flags via showme) to find
> > the Right shared libraries.
> >
> > Let us know if that works for you.
> >
> > FWIW, we do recommend using the wrapper compilers over extracting the
> > flags via --showme whenever possible (it's just simpler and should do
> > what you need).
> >
> >
> > On Feb 15, 2007, at 3:38 PM, Eric Thibodeau wrote:
> >
> > > Hello all,
> > >
> > >
> > > I have been attempting to compile mpptest on my nodes in vain. Here
> > > is my current setup:
> > >
> > >
> > > Openmpi is in "$HOME/openmpi_`uname -m`" which translates to "/
> > > export/home/eric/openmpi_i686/". I tried the following approaches
> > > (you can see some of these were out of desperation):
> > >
> > >
> > > CFLAGS=`mpicc --showme:compile` LDFLAGS=`mpicc --showme:link` ./
> > > configure
> > >
> > >
> > > Configure fails on:
> > >
> > > checking whether the C compiler works... configure: error: cannot
> > > run C compiled programs.
> > >
> > >
> > > The log shows that:
> > >
> > > ./a.out: error while loading shared libraries: liborte.so.0: cannot
> > > open shared object file: No such file or directory
> > >
> > >
> > >
> > > CC="/export/home/eric/openmpi_i686/bin/mpicc" ./configure --with-
> > > mpi=$HOME/openmpi_`uname -m`
> > >
> > > Same problems as above...
> > >
> > >
> > > LDFLAGS="$HOME/openmpi_`uname -m`/lib" ./configure --with-mpi=$HOME/
> > > openmpi_`uname -m`
> > >
> > >
> > > Configure fails on:
> > >
> > > checking for C compiler default output file name... configure:
> > > error: C compiler cannot create executables
> > >
> > >
> > > And...finally (not that all of this was done in the presented order):
> > >
> > > ./configure --with-mpi=$HOME/openmpi_`uname -m`
> > >
> > >
> > > Which ends with:
> > >
> > >
> > > checking for library containing MPI_Init... no
> > >
> > > configure: error: Could not find MPI library
> > >
> > >
> > > Anyone can help me with this one...?
> > >
> > >
> > > Note that LAM-MPI is also installed on these systems...
> > >
> > >
> > > Eric Thibodeau
> > >
> > >
> > > _______________________________________________
> > > users mailing list
> > > users_at_[hidden]
> > > http://www.open-mpi.org/mailman/listinfo.cgi/users
> >
> >
> >
>
> _______________________________________________
> users mailing list
> users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>