Enclosed is a gzipped tar file (lam-711.tar.gz)
containing all outputs from building lam v.7.1.1.
As you can find in the config.log file, I was using TCP
for RPI. The hardware is GNU/Linux x86 AMD Athlon.
There are two things that I'd like to know:
(1) There is no problem builidng LAM v.7.1.1 with tcp
with or without memory manager under Linux.
However, when I attempted to build "static" binaries
from a C++ package using the lam/mpi, it suffers memory
manager problem, and failed to make static executables.
This problem was not seen under Sun Solaris.
Then, which RPI should I use under Linux to avoid this
problem? (I'd just like to make sure that the lam was
configured appropriately.)
(2) There was no core file. Is there any way to force it
to be dumped?
I'd be grateful for any help.
-Phil
--- Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Nov 30, 2005, at 4:40 PM, Jeff Squyres wrote:
>
> > What RPI were you using? Note that using the ib or gm
> RPI *requires*
> > to use of the memory manager.
>
> Wait -- I stand corrected here. The gm RPI does *not*
> require the use
> of the memory manager because of Solaris. If you do not
> use a memory
> manager with gm, LAM falls back to pinning / unpinning on
> the fly.
>
> The same is not true for the ib RPI -- it requires the
> use of the
> memory manager.
>
> Sorry for the confusion.
>
> --
> {+} Jeff Squyres
> {+} The Open MPI Project
> {+} http://www.open-mpi.org/
>
> _______________________________________________
> This list is archived at
> http://www.lam-mpi.org/MailArchives/lam/
>
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
|
