From: Garrett C. <yan...@gm...> - 2011-07-06 22:21:00
|
Hi, As part of the a work project, I've tasked myself to upgrade net-snmp from an older version to a newer version. One of the things that has occurred recently on FreeBSD is the netinet, et all headers have been shuffled, which has uncovered a fair amount of breakage with the autoconf tests on FreeBSD. Trying to fix that I've looked at fixing support on some of the other BSDs (Net, Open), and I noticed with the latest release of Open (at least) with the default settings when building from svn (I didn't realize everything had been shuffled over to git at the time) that the build was broken with some missing symbols/bad #defines. I'm going through and fixing things as I can internally, creating patch 'sightings' as needed on sf.net (I was silly and filed some patches under bug reports before I realized there were separate queues for bugs and patches), but if the developers have any guidance for what needs to be done to clean things up, that would be more than welcome. The OS-dependent code is messy and my personal feeling is that it should be properly refactored to avoid , and antiquated OS support should be removed (FreeBSD 5.x has been dead for some time for instance, and FreeBSD 6.x is no longer supported, etc), but these are just some other thoughts I had w.r.t. net-snmp and OS support. Thanks! -Garrett |