ERROR: Command returned a non-zero exist status (trunk):
make distcheck
Start time: Thu Feb 18 21:01:04 EST 2010
End time: Thu Feb 18 21:02:52 EST 2010
===
[... previous lines snipped ...]
make[2]: Entering directory
Hi folks
I've had a few recent inquiries about more scalable launch methods for OMPI. It
rapidly became clear that I had never documented the modex-less launch
operations in the OMPI trunk, and that many people were unaware of their
existence.
So...I finally wrote a wiki page on the subject:
On Feb 18, 2010, at 1:12 PM, Ethan Mallove wrote:
> About this change - I have been seeing the below error while trying to
> build the trunk recently:
>
> $ make ...
> cd . && /bin/bash /tmp/config-missing-bug-in-trunk/trunk/config/missing
> --run aclocal-1.10 -I config
>
About this change - I have been seeing the below error while trying to
build the trunk recently:
$ make ...
cd . && /bin/bash /tmp/config-missing-bug-in-trunk/trunk/config/missing --run
aclocal-1.10 -I config
configure.ac:939: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
WHAT: Add pkg-config(1) data files for Open MPI
WHY: pkg-config is a de facto Linux standard. At least one user asked for it;
it was easy to do
WHERE: */config/config_files.m4, */tools/wrappers
WHEN: Can be for 1.5 or 1.5.1; I don't really have a strong opinion
TIMEOUT: Next Tuesday teleconf
On Feb 18, 2010, at 1:53 AM, Ralf Wildenhues wrote:
> You could probably create fake empty libopen-rte and libopen-pal stub
> libraries with 0:0:0 purely for the sake of allowing such an a.out to
> still work (on systems with versioned sonames[1]). Since this doesn't
> actually use any of the
On Wed, 2010-02-17 at 17:14 -0500, Jeff Squyres wrote:
> Looks good to me!
>
> Please commit and file CMRs for v1.4 and v1.5 (assuming this patch applies
> cleanly to both branches).
Not sure I have the rights to do these things?
Regards,
Nadia
>
>
> On Feb 16, 2010, at 6:46 AM, Nadia Derbey
* Jeff Squyres wrote on Wed, Feb 17, 2010 at 11:51:42PM CET:
> On Feb 17, 2010, at 3:05 PM, Ralf Wildenhues wrote:
>
> > > The issue is that if the user has to specify -static to their linker,
> > > they *also* have to specify --ompi:static, or Bad Things will happen.
> > > Or, if they don't
