-----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_ignore? I posted a similar message to MTT-Users and a couple concerns were brought up which I will address below. Jeff Squyres 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 I doubt anyone would > object. The situation at present is that the SCTP BTL only builds on FreeBSD, OSX and Linux and only if the SCTP is found to be in a standard place. On Linux, for instance, you need to have installed the lksctp package in order for the SCTP BTL to build. We also have a --with-sctp configure option where you can specify the SCTP path should it not be in a standard location. If SCTP does not exist on the system, then the BTL will not build and more importantly, will not break the build of the overall system. My question now, is it necessary for us to alter the above behavior (as initially mentioned by Jeff), or is having the SCTP BTL build iff SCTP is found sufficient? Thanks in advance for any advice on this matter. - -- Karol Mroz km...@cs.ubc.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTvM9uoug78g/Mz8RAubuAJ9g7BShXIaYJCetVA9OWOFIqtUDAgCdFU+6 2TF/mgeTaJr1hfB7AP3Evb4= =+aH4 -----END PGP SIGNATURE-----
