BTW, if people want to rename openib btl to something else and then change the configure scripts - I'm ok. About naming - I would agree with Terry, it makes sense to name it after network API used for this btl - "verbs" (it is not ibverbs).
Bottom line, I would recommend to keep configure option naming in sync with component (in this case BTL) naming. Pavel (Pasha) Shamis --- Application Performance Tools Group Computer Science and Math Division Oak Ridge National Laboratory On Jun 21, 2012, at 9:30 AM, Jeff Squyres wrote: > On Jun 21, 2012, at 9:16 AM, Jeff Squyres wrote: > >> 2. Have consistent behavior between the configury of all OFED-lovin' >> components (currently the 4 I listed), per your description: >> * --with-openfabrics[=DIR] means that all OFED-lovin' components must >> configure successfully, or fail >> * --without-openfabrics means that all OFED-lovin' component must not build > > > I'm sorry -- that's not quite correct. > > hwloc will build regardless of whether you specify --with-openfabrics or not > (because it doesn't *need* OpenFabrics support). > > But the other 3 OpenFabrics-based components (ofud, ud, openib) must all > succeed if --with-openfabrics is specified, and will not be built if > --without-openfabrics is specified. Because all of these components *need* > OpenFabrics support -- they cannot build without OF support. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
