On Dec 1, 2005, at 10:52 PM, Phil Yoon wrote:
> Enclosed is a gzipped tar file (lam-711.tar.gz)
> containing all outputs from building lam v.7.1.1.
Sorry for the delay in replying. I recently upgraded my laptop, and
my new mail client hid a lot of mail from me. :-(
> 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.
Can you be more specific about what problems occurred about "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.)
The TCP RPI does not require the memory manager.
> (2) There was no core file. Is there any way to force it
> to be dumped?
Check your limits and see what the limit for corefiles are (you may
need to set this is shell startup files so that it propagates to all
nodes). For example, if you're a bash used, set "ulimit -c
unlimited" to make full corefiles. See the bash man page for details.
--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/
|
