Hmm. Already, this small feature is beginning to look unattractive. :-\ I see how libnuma is Linux-specific; but is the level of memory binding uniform across all other OS's? I.e., do we need to print the same kind of granularity of memory support for other OS's?
On Nov 30, 2011, at 5:13 AM, bgog...@osl.iu.edu wrote: > Author: bgoglin > Date: 2011-11-30 05:13:49 EST (Wed, 30 Nov 2011) > New Revision: 4006 > URL: https://svn.open-mpi.org/trac/hwloc/changeset/4006 > > Log: > Only show Memory support status at the end of configure on Linux > > We only print Linux-specific features there, we don't want to show > "none" on other OSes if it's wrong. > > > Text files modified: > trunk/configure.ac | 9 +++++++++ > 1 files changed, 9 insertions(+), 0 deletions(-) > > Modified: trunk/configure.ac > ============================================================================== > --- trunk/configure.ac (original) > +++ trunk/configure.ac 2011-11-30 05:13:49 EST (Wed, 30 Nov 2011) > @@ -183,6 +183,7 @@ > [append_env hwloc_numa_status "migrate pages"]) > AS_IF([test "$hwloc_numa_status" = ""], [hwloc_numa_status=none]) > > +# Beginning of generic support > cat <<EOF > > ----------------------------------------------------------------------------- > @@ -191,7 +192,15 @@ > Probe / display PCI devices: $hwloc_pci_happy > Graphical output (Cairo): $hwloc_cairo_happy > XML input / output: $hwloc_xml_status > +EOF > + > +# Linux specific support > +AS_IF([test "$hwloc_linux" = "yes"], [cat <<EOF > Memory support: $hwloc_numa_status > +EOF]) > + > +# End of generic support > +cat <<EOF > ----------------------------------------------------------------------------- > > EOF > _______________________________________________ > hwloc-svn mailing list > hwloc-...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-svn -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
