As it is not listed on http://www.open-mpi.org/projects/hwloc/ nor
does it use a standard operating system (although CNK is POSIX and
very Linux-like in general), I didn't have a reasonable expectation
that it would work without some development, but I verified that some
of the tests fail, just to be sure.

Fortunately, almost all of the tests passed, except for glibc-sched
and hwloc_bind. I suspect this is due to the various
incompatibilities between glibc in CNK vs. Linux. The failure of both
tests occurs with XLC and GCC, although I report the details below for
XLC only.

Should I report this as a bug? Is it sufficient to port to Blue
Gene/Q if I provide the kernel API calls related to thread location,
etc. or would any hwloc developers be interested in Blue Gene/Q access
for the purposes of development and testing?

Info: stdin received from /dev/null
Info: stdout sent to
/veas_home/jhammond/HWLOC/hwloc-1.4.2rc1/build/tests/16927.output
Info: stderr sent to
/veas_home/jhammond/HWLOC/hwloc-1.4.2rc1/build/tests/16927.error

Info: stdin received from /dev/null
Info: stdout sent to
/veas_home/jhammond/HWLOC/hwloc-1.4.2rc1/build/tests/16912.output
Info: stderr sent to
/veas_home/jhammond/HWLOC/hwloc-1.4.2rc1/build/tests/16912.error