sorry, I found the issue, and it's not with lam-mpi. Thanks!
On 8/12/05, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> Not offhand, no. Can you send the information listed on
> http://www.lam-mpi.org/using/support/?
>
> Thanks!
>
> On Aug 11, 2005, at 2:43 PM, David Cummings wrote:
>
> > Hello all,
> > This question isn't entirely lam-mpi specific, though I get the
> > feeling I may get some useful help here anyway. I am trying to run
> > lam-mpi on an SGI O2k(8cpu cc-numa) running n32 Linux. With the
> > default ./configure options, lam cannot detect the shared memory and
> > thus doesn't compile the sysv or usysv rpi modules. It cannot
> > determine maxalloc and poolsize. When I set these the build goes
> > smoothly, though my program exits with a non-zero value due to
> > MPI_INIT failing. Before we get into my lam config's, I was wondering
> > if anyone could provide me with some test code to make sure my shmem
> > what-not is set up correctly. Thanks
> > -Dave
> > --
> > The way that can be named is not the Way.
> >
> > _______________________________________________
> > This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> >
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
The way that can be named is not the Way.
|
