On Wed, Dec 08, 2010 at 10:29:58PM +0100, Niels Baggesen wrote: > The following patch (for V5-6-patches and trunk) allows to configure > with --disable-debugging > > --- agent/mibgroup/agent_mibs.h (revision 19730) > +++ agent/mibgroup/agent_mibs.h (working copy) > @@ -1,6 +1,8 @@ > config_require(agent/nsTransactionTable) > config_require(agent/nsModuleTable) > +#ifndef NETSNMP_NO_DEBUGGING > config_require(agent/nsDebug) > +#endif > config_require(agent/nsCache) > config_require(agent/nsLogging) > config_require(agent/nsVacmAccessTable)
Is the need to say "require these modules if possible" a common case? This is the problem the above patch tries to solve but the problem is that the knowledge of wether it is possible to include module X realy shoud be in X and not in Y-that-suggests-X. Is the need to say "require at least one of theese modules, try them in the listed order" a common case? This is a variant of the above case where Y-needs-X-or-Z. A prime example is the tunnel mib that need either if-mib/ifTable/ifTable or mibII/interfaces but those two modules do confict with each other. Now this patch points to another problem: You can't configure with --with-mib-modules=agent/nsDebug since that would trigger the very problem that the patch tries to prevent so I think an #ifdef NETSNMP_NO_DEBUGGING config_error(Something) #endif should be added to agent/nsDebug.h /MF ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
