The build machine at IU was running out of disk space.
I'm not 100% sure that this is the underlying error, but I'm going to kick off
another build and see if we get the same dist error. If so, I'll dig more.
On Feb 7, 2010, at 9:13 PM, MPI Team wrote:
>
> ERROR: Command returned a non-zero
Yay. :-)
On Feb 8, 2010, at 4:28 PM, MPI Team wrote:
> Creating nightly snapshot SVN tarball was a success.
>
> Snapshot: 1.7a1r22577
> Start time: Mon Feb 8 15:56:14 EST 2010
> End time: Mon Feb 8 16:28:48 EST 2010
>
> Your friendly daemon,
> Cyrador
> __
It looks like this is fixed now. Let us know if you see any other
issues with it.
-- Josh
On Feb 5, 2010, at 11:10 AM, Jeff Squyres wrote:
IU has been having some problems with this -- let me ping the admin
and see what happened (I also saw your commit go by and noticed that
no CMR ticket
How about
--enable-mpi-threads ==> --enable-multi-threads
ENABLE_MPI_THREADS ==>ENABLE_MULTI_THREADS
Essentially, s/mpi/multi/ig. This gives us "progress thread" support and
"multi thread" support. Similar, but different.
Another possibility instead of "mpi" could be "concurrent
Well, does --disable-multi-threads disable progress threads? And do you want
to disable thread support in ORTE because you don't want MPI_THREAD_MULTIPLE?
Perhaps a third option is a rational way to go?
Brain
On Feb 8, 2010, at 6:54 PM, Jeff Squyres wrote:
> How about
>
> --enable-mpi-thr
