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 used --with-libnuma=/usr since Prentice Bisbal's suggestion and it
worked. Unfortunately, I found no way to fix the failure in finding
libimf.so when compiling openmpi-1.3.1 with intels, as you have seen
in other e-mail from me. And gnu compilers (which work well with both
openmpi and the slower code of my application) are defeated by the
faster code of my application. With limited hardware resources, I must
rely on that 40% speeding up.
My post how to implement the -rpath flag, which should fix the
libimf.so problem, has found no answer. And i found no help through
google. If you have a suggestion on that it would be great.
I was referring to the following notes: "However, dynamic linkage is
also a headache in that the mechanisms
used to find shared libraries during dynamic loading are not all that robust
on Linux systems running MPICH or other MPI packages. Typically the
LOAD_LIBRARY_PATH environment variable will be used to find shared libraries
during loading, but this variable is not reliably propagated to all processes.
For this reason, for the compilers that use compiler shared libraries (ifort,
pathscale), we use LD_LIBRARY_PATH during configuration to set an -rpath
linkage option, which is reliably available in the executable. This works
well as long as you insure that the path is the same for all machines running
pmemd. Earlier versions of ifort actually also set -rpath, but this was
dropped due to confusing error messages when ifort is executed without
On Wed, Apr 15, 2009 at 1:04 PM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Apr 6, 2009, at 4:24 PM, Prentice Bisbal wrote:
>> > I would appreciate help in circumventing the problem.
>> I believe you need
> Sorry for the late reply.
> FWIW, the above is correct -- you should use --with-libnuma=/usr, not
> Please also note in this thread:
> Â Â http://www.open-mpi.org/community/lists/users/2009/04/8853.php
> We found some obscure logic issues with the handling of --with-libnuma. Â I
> doubt that those should affect you (since you're mentioning an explicit
> directory for libnuma), but I mention it to be complete.
> Jeff Squyres
> Cisco Systems
> users mailing list