Disregard this -- I forgot (and read the configure output wrong) that hwloc will *not* do #2 (i.e., link against libpci) unless you specifically request it via --enable-libpci.
I'm assuming that we do *not* want to enable that by default (i.e., so that the compiled OMPI installation does not accidentally become GPL tainted).
On Mar 18, 2013, at 1:57 PM, "Jeff Squyres (jsquyres)" <jsquyres_at_[hidden]>
> (*** Sam: please add this to the agenda for tomorrow; thanks ***)
> If you recall, we recently discovered that hwloc was linking against libpci, which is GPL (not LGPL). This introduced GPL taint into hwloc, and therefore into Open MPI. ** Note that we didn't have any released versions of Open MPI that exhibited this behavior, so we're ok.
> New versions of hwloc (e.g., v1.5.2) have been released with support for libpciaccess -- a BSD library that provides the PCI stuff that hwloc needs. However, hwloc still also provides support for libpci, too. Right now, hwloc's configury does something like this:
> 1. if libpciaccess is found, use it
> 2. if libpciaccess is not found, if libpci is found use it
> 3. if neither are found, disable PCI support
> Do we want to allow #2? (by default, at least)
> I ask because I don't know if various distros still have libpci installed by default, not libpciaccess (e.g., my RHEL6 installs seem to be configured this way). Because if they do, then OMPI compiled on those systems will be GPL tainted -- and the user may not know. In many cases, this may not matter, but this could be a big deal for ISVs or other OMPI-binary distributors.
> Jeff Squyres
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
> devel mailing list
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/