I think that it would be possible to say something like:
While hwloc is BSD licensed, it may potentially link to libraries with
more restrictive license terms.
However, that is more or less true of ANY software.
For instance, if I compile some BSD licensed software on AIX with '-static'
then IBM's libc ends up in my binary.
I am not saying that IBM's libc poses any specific issues, just using it as
So, this is in no way a unique situation for hwloc.
I think that if hwloc were to explicitly list libpci then we start a
dangerous precedent under which users may expect us to continuously "audit"
the libs used on various systems.
On Tue, Feb 5, 2013 at 1:50 PM, Jeff Squyres (jsquyres)
> It was just pointed out to me that libpci is licensed under the GPL (not
> the LGPL).
> Hence, even though hwloc is BSD, if it links to libpci.*, it's tainted.
> IANAL, this is not legal advice, yadda yadda yadda. But does this jive
> with other peoples' understanding?
> This has caused a problem for an unnamed vendor who wanted to ship a
> binary tool that linked against libhwloc (that linked against libpci).
> The complaint to me was that hwloc needs to be clearer about this in its
> Does this sound right?
> Jeff Squyres
> For corporate legal information go to:
> hwloc-devel mailing list
Paul H. Hargrove PHHargrove_at_[hidden]
Future Technologies Group
Computer and Data Sciences Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900