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.
I built and installed both MPICH2 and openMPI from source, so no
distribution packages or anything. MPICH2 has the modules located in
/usr/local/include, which I assume would be found (since its in my
path), were it not for specifying -I$OPENMPI_HOME/lib at compile time,
right? I can't imagine that if you tell it where to look for the
correct modules, it would search through your path first before going
to where you tell it to go. Or am I too optimistic? Thanks again for
On Mon, Sep 22, 2008 at 8:58 AM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Sep 22, 2008, at 10:10 AM, Brian Harker wrote:
>> Thanks for the reply...crap, $HOME/openmpi/lib does contains all the
>> various lilbmpi* files as well as mpi.mod,
> That should be correct.
>> but still get the same
>> error at compile-time. Yes, I made sure to specifically build openMPI
>> with ifort 10.1.012, and did run the --showme command right after
>> installation to make sure the wrapper compiler was using ifort as
> Ok, good.
>> Before posting to this mailing list, I did uninstall and re-install
>> openMPI several times to make sure I had a clean install. Still no
>> luck. :(
> Ok. Have you checked around your machine to ensure that there is no other
> mpi.mod that the compiler is finding first? E.g., in your MPICH2
> installation? Or is Open MPI installed by your distro, perchance? You
> might want to try a "rpm -qa | grep openmpi" (or whatever your distro's
> equivalent is to check already-installed packages).
> Jeff Squyres
> Cisco Systems
> users mailing list
"In science, there is only physics; all the rest is stamp-collecting."