Re: On the nature of backward comparability
Bart Van Assche <[email protected]>
| Newsgroups | gmane.network.net-snmp.devel |
|---|---|
| Message-ID | <[email protected]> |
On 05/14/18 14:07, Wes Hardaker via Net-snmp-coders wrote:
> [Note that with all the above, we also had to deal with the desire to
> keep SNMP code stacks small. We still get requests for people that
> don't want any openssl code in their compiled system because auditing is
> worse, and --enable-mini-agent is very popular still, as is
> --enable-read-only and --enable-minimalist). In fact, most of those
> features were actually paid for which is important to understand because
> when multiple organizations put money up to make a code-base reduce as
> small as possible it must lead to the conclusion that compiled code
> reduction is an important element.]
Hello Wes,
Is there perhaps a list available of the MIBs that are compatible with
--enable-read-only, --enable-mini-agent and --enable-minimalist? Most
MIBs that are not enabled by default fail to build with one of these
options enabled. Even if I do not enable any additional MIBs building
with --enable-read-only fails on the master branch:
snmpping.c: In function ‘cleanup_ctlTable’:
snmpping.c:276:27: error: ‘SNMP_MSG_SET’ undeclared (first use in this
function)
pdu = snmp_pdu_create(SNMP_MSG_SET);
^
snmpping.c:276:27: note: each undeclared identifier is reported only
once for each function it appears in
Is this a known issue?
Thanks,
Bart.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders