William --
It looks like the memory manager that LAM is using is not playing well
with BSD (in fairness, I don't think we ever tested it on BSD [other
than OSX, which is a slightly different ballgame]). Check out the
release notes about this in the LAM/MPI Installation Guide (in your
tarball and http://www.lam-mpi.org/using/docs/).
If you're not using Myrinet or Infiniband, you don't need this memory
manager anyway, so you can configure LAM with:
--with-memory-manager=none
Let me know if this solves your problems.
On Mar 29, 2005, at 3:33 AM, Ralf Wildenhues wrote:
> Hi William,
>
> * William Bierman wrote on Tue, Mar 29, 2005 at 10:01:52AM CEST:
>> bill_at_c1:~
>> $ mpicc -showme -o h hello.c
>> gcc -I/usr/local/include -pthread -o h hello.c -L/usr/local/lib
>> -llammpio -llamf77mpi -lmpi -llam -lutil
>
> Looks sane.
>
>> The backtrace showed pthread functions. Perhaps LAM doesn't play well
>> with pthreads on FreeBSD?
>>
>> On Tue, 29 Mar 2005 09:47:19 +0200, Ralf Wildenhues
>> <Ralf.Wildenhues_at_[hidden]> wrote:
>>
>>> Please show what mpicc invokes. If you compiled lam yourself, show
>>> how
>>> you configured it.
>>
>> I did not pass any parameters to ./configure, so it used its defaults.
>> Is there a file I can attach, perhaps lam_config.h, which will best
>> define the decisions it made?
>
> I have no idea what's going on here. The HISTORY file in svn shows
> some
> pthread-related changes after 7.1.1, maybe they could be relevant to
> your
> problem. You might want to try the svn version of LAM or the latest
> snapshot. If the problem persists, please see the recommended steps[1]
> for providing sufficient information for a bug report.
>
> Regards,
> Ralf
>
> [1] http://www.lam-mpi.org/using/support/
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
