Do you already use hwloc's PCI objects in OMPI v1.7 ? Brice
Le 06/02/2013 15:39, Jeff Squyres (jsquyres) a écrit : > BEFORE YOU PANIC: this only affects Open MPI v1.7 (which is not yet released) > and the OMPI SVN trunk (which is also, obviously, not released). ***OMPI > v1.6.x is unaffected/not GPL tainted*** > > Here's the full details: > > It was just discovered yesterday that libpci, which hwloc links against for > PCI device detection, is GPL (not LGPL). IANAL / this is not legal advice, > but my humble understanding is that this introduces GPL taint to hwloc. And > since OMPI links in hwloc, it is also tainted. This is problematic for > vendors who want to ship binaries linked against Open MPI. > > * The as-yet-unreleased OMPI v1.7 (and trunk) embeds hwloc v1.5.1, and > utilizes hwloc PCI device detection (thereby linking in libpci). Bad. > * The OMPI v1.6 series embeds hwloc v1.3.2, and explicitly disables hwloc's > PCI device detection (thereby NOT linking in libpci) because of compatibility > problems with Solaris. Good. > > Hence, from a released-version perspective, I think OMPI is in the clear. > However, we can't release 1.7 until this is fixed. > > The good news is that within hours of discovering the issue, the hwloc guys > issued a preliminary patch to change hwloc to use libpciaccess (vs. libpci), > which is BSD-licensed. They are working on firming up this patch in order to > release new versions of hwloc to remove the default-build options of > libpci/GPL taint. > > I will update OMPI's SVN trunk and submit a v1.7 CMR when this is ready. I > imagine it will take at least a few days. >
