On Dec 5, 2007, at 1:42 PM, Karol Mroz wrote:
Removal of .ompi_ignore should not create build problems for anyone
who
is running without some form of SCTP support. To test this claim, we
built Open MPI with .ompi_ignore removed and no SCTP support on
both an
ubuntu linux and an OSX machine.
Hi...
Karol Mroz wrote:
> Removal of .ompi_ignore should not create build problems for anyone who
> is running without some form of SCTP support. To test this claim, we
> built Open MPI with .ompi_ignore removed and no SCTP support on both an
> ubuntu linux and an OSX machine. Both builds succeed
On Nov 30, 2007, at 6:51 PM, Karol Mroz wrote:
A couple other questions we had, and this references an email from a
while back, deals with SCTP BTL exclusivity. I will link the relevant
message below and any advice would be appreciated:
http://www.open-mpi.org/community/lists/devel/2007/11/2609.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Jeff... thanks for getting back to me.
Jeff Squyres wrote:
> On Nov 29, 2007, at 12:13 PM, Karol Mroz wrote:
>
>>> One solution might be to remove the .ompi_ignore but to only enable
>>> the SCTP BTL when an explicit --with-sctp flag is given to
On Nov 29, 2007, at 12:13 PM, Karol Mroz wrote:
One solution might be to remove the .ompi_ignore but to only enable
the SCTP BTL when an explicit --with-sctp flag is given to configure
(or something similar). You might want to run this by the [OMPI]
group first, but there's precedent for it, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Good morning...
So Brad Penoff and I would like begin MTT tests of the SCTP BTL, but due
to the presence of the .ompi_ignore file, the SCTP BTL source is not
included in nightly tarballs. I was curious if anyone would object to
our removing .ompi_igno
