LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2004-09-21 11:43:36


On Sep 21, 2004, at 8:48 AM, Rob Malpass wrote:

> At long last, here's the output from configure and make. If anyone
> can make sense of this, I'd be grateful.
> [snipped]
> .libs/libmpi.lax/libpmpi.a/pwgetname_f.o
> .libs/libmpi.lax/libpmpi.a/pwgroup_f.o
> .libs/libmpi.lax/libpmpi.a/pwpost_f.o
> .libs/libmpi.lax/libpmpi.a/pwsetattr_f.o
> .libs/libmpi.lax/libpmpi.a/pwseterr_f.o
> .libs/libmpi.lax/libpmpi.a/pwsetname_f.o
> .libs/libmpi.lax/libpmpi.a/pwstart_f.o
> .libs/libmpi.lax/libpmpi.a/pwtick_f.o
> .libs/libmpi.lax/libpmpi.a/pwtime_f.o
> .libs/libmpi.lax/libpmpi.a/pwwait_f.o
> make[2]: *** [libmpi.la] Error 137
> make[2]: Leaving directory `/home/rob/lam-7.1/share/libmpi'

I'm a little confused -- the errors that you sent before were about
laminfo, not libmpi itself. Did something change?

I don't know what an error 137 is from gcc; it could well be that it is
running out of memory here because that's the massive "make libmpi"
step -- you can see how many .o files are involved. Two options here:

1. try increasing your virtual memory and see if that helps
2. compile all the SSI modules dynamically; use the following configure
switches "--enable-shared --disable-static --with-modules". The
resulting libmpi is a bunch smaller -- each SSI module becomes its own
.so and is loaded at runtime (as necessary).

Does that help?

-- 
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/