Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Brian Barrett (bbarrett_at_[hidden])
Date: 2007-04-09 11:24:15

On Apr 7, 2007, at 12:59 AM, Brian Powell wrote:

> Greetings,
> I turn to the assistance of the OpenMPI wizards. I have compiled
> v1.2 using gcc and ifort (see the attached config.log) with a
> variety of options. The compilation finishes (side note: I had to
> define NM otherwise the configure script failed) and installs. I
> try to run ompi_info and get the following:
> ----------------------------------------------------------------------
> ----
> A library call unexpectedly failed. This is a terminal error; please
> show this message to an Open MPI wizard:
> Library call: mca_base_open
> Source file:
> Source line number: 139
> Aborting...
> ----------------------------------------------------------------------
> ----

For reasons I can't duplicate, you're getting an out of memory error
when trying to initialize our component system. I haven't seen this
one before, but I noticed a couple of things in the config.log that
made me think there might be an underlying problem...

1) You should never have to specify NM on OS X, even when cross-
compiling. Can you send information on why this is necessary?

2) This might actually be the answer to #1, but you shouldn't specify
--build=i386. The --build argument takes a complete config.guess-
style architecture. In the case of Mac OS X 10.4.9 on i386, that
would be: i386-apple-darwin8.9.1. But unless you're cross compiling,
that argument should not be necessary.

3) The sysroot stuff is really on necessary if you are cross-
compiling. I wouldn't use it in other cases, as it seems to make
things more fragile. If you're going to specify a sysroot, you need
to specify it in CFLAGS, CXXFLAGS, and OBJCFLAGS. You also should
specify the -arch i386 in CXXFLAGS and OBJCFLAGS if you are going to
specify it in CFLAGS and FFLAGS, if only for consistency.

If you could try recompiling without the --build argument and let me
know if that fixes the problem, I'd appreciate it.