On Feb 1, 2005, at 12:11 PM, Ed Zaron wrote:
> Thanks for your suggestion, Christian, I'll try it.
>
> Brian, I have attached the gzipped output of lamtests-7.1.1/config.log
Ok, I see the problem now (and apologize for not seeing it in the first
place...). There is are a couple of bugs in LAM 7.1.1 that only crop
up on OS X. One of them is a unresolved symbol issue when using the XL
compiler suite. In order to support high speed interconnects, we need
to add some hooks into the OS X memory manager. I goofed when adding
the code, such that the flags are removed by XLC/XLF before they get
passed to the linker and turned into a file argument, which means
XLC/XLF choke when trying to link anything.
The workaround (assuming you don't need Myrinet or InfiniBand support)
is to configure LAM itself with the option --with-memory-manager=none .
This will disable the code that breaks XLF. If you need Myrinet or
InfiniBand support, LAM 7.1.2b12 (http://www.lam-mpi.org/beta/) fixes
the issue.
One other note - the usysv RPI on SMP G5 machines (G4 machines and
single processor G5s should be unaffected) is susceptible to data
corruption in certain circumstances. We have fixed the problem in LAM
7.1.2b12, but there is no workaround in 7.1.1. If you need a stable
MPI platform, we recommend using the sysv RPI instead of usysv until
the release of LAM 7.1.2.
Hope this helps,
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
