Ah, that might explain it, then.
I guess this means we need to add a few configure tests to figure out the dependencies of libpci (if any). Yuck.
Do we have any idea what function in libpci is calling the resolver functionality?
On Jun 13, 2011, at 8:42 AM, Christopher Samuel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 13/06/11 22:22, Jeff Squyres wrote:
>> Chris -- does nm on your libpci not show this?
> Nope, there is no libpci.so* on RHEL5.6, just a libpci.a.
> (and no, I've no idea why either!)
> - --
> Christopher Samuel - Senior Systems Administrator
> VLSCI - Victorian Life Sciences Computation Initiative
> Email: samuel_at_[hidden] Phone: +61 (0)3 903 55545
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> hwloc-devel mailing list
For corporate legal information go to: