On Fri, 2 Jan 2026, 12:47 pm Magnus Fromreide, <[email protected]> wrote:
> On Thu, Dec 25, 2025 at 03:23:34PM -0800, Wes Hardaker via Net-snmp-coders > wrote: > > Bart Van Assche via Net-snmp-coders > > <[email protected]> writes: > > > > > One possible solution is to modify net-snmp-config such that all -W > > > flags are filtered out. There may be better solutions. > > > > IMHO, the --enable-developer was created for adding options like this > > and they should never be on anywhere in default builds. We should > > remove all warning flags everywhere by default (IMHO, but that's the > > point of a discussion: I could be alone in my thinking). > > I am stronly agreeing and wants to go further - I think all dialect options > should be removed from the net-snmp-config output, so no more > > -g > -fno-strict-aliasing > -O2 > > as that should be the the choice of the client program, not us. I would like that very much. As an example of the issue adding those options causes, syslog-ng failed to compile with 5.9.5.2 but compiled ok. What happens is one of the options triggered a compile error in the syslog-ng code itself because a previous warning was now an error. So changing the version of net-snmp a program links to caused an error so it wouldn't compile; but not due to an API change. - Craig
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
