On 14 April 2010 11:16, Bart Van Assche <[email protected]> wrote:
> But what I do not like is that the
> patch disables the notification log MIB for all Win32 builds.
But as far as I can tell, the problem was that the notification log MIB
was *not* included in the Win32 build. But the header file claimed
that it was. Hence the errors.
It would probably be helpful to be explicit about
a) which branch(es) you are referring to
b) what build mechanism(s) and option(s) you are using
c) what version(s) of build software you are using
As far as I can tell, this code is only referenced in the following build files:
libnetsnmptrapd:
DSP file (MSVC interactive build?)
Makefile (build.bat)
snmptrapd
Makefile (build.bat)
netsnmpmibssdk (5.3.x & 5.4.x)
DSP file only
(but not in the non-SDK netsnmpmibs DSP file)
netsnmpmibs (5.5 and trunk)
DSP file
snmpd (5.5 and trunk)
Makefile
(And not at all in the 5.2.x tree)
So up until 5.5, there seems to be an inconsistency between
the interactive build environment and the 'build.bat' setup.
> If I do not
> receive any further comments, I'll prepare and post a patch for the V5.4
> branch that makes win32/build.bat work and keeps the notification log MIB in
> the Win32 builds.
I am more than slightly concerned about adding support for the
notification log MIB in at this late stage - particularly in environments
where it was not present before.
I _had_ been intended to try and roll out rc3 candidates tomorrow,
with the hope of being able to release these as the final versions
when I got back from holiday. It's looking increasingly likely that
this is not going to be feasible. (Or not for 5.4.3, at least)
I can't help feeling that we should really have been having this
discussion several weeks ago. Don't get me wrong - I'm not trying
to get at you, Bart. It's good that you've picked up these problems now.
But I find it incomprehensible that the build.bat mechanism has
been fundamentally broken for so long (presumably ever since
MSVC 2008 appeared), and that none of the three pre-release
calls (nor the first release candidate) picked up on this.
It does lead me to question how many people actually took note
of those earlier calls - and why we even bother!
Dave
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
