On Wed, 2013-04-10 at 09:03 +1000, Craig Small wrote: > The right way is to use a --with-blah (--with-numa ?) to enable to > feature and then have configure check for the presence of that dev > library and headers. The configure should fail if they are not found. > Hmm, it might be --enable-numa, its a but unclear. > --with--blah means link with library blah, --enable-blah means turn on > feature blah. It's sort of both so perhaps doesn't matter. > > The packagers then ensure that if they have enabled this feature that > they pull in the required library (Debian does this with dpkg-shlibdeps > which is run at build time) Hi Craig, I tried to set up configure so it would not fail rather than impose a new dependency. Thus, procps-ng adapts to a wider variety of environments. Our goal is twofold: 1) Somehow suggest/coax/insist on numa.h and libnuma at build time. 2) Ensure procps will ship with libnuma (only) so users have access to the new '2' and '3' provisions. Can this be done? Jim