On Tue, May 4, 2010 at 3:00 PM, Ron Bets <[email protected]> wrote:
> Thanks. I am not tied specifically to the 5.4.x stream. My main > requirement is support for IPv6 transport on Windows, Solaris, and Linux. > Would I be better off with a different release? I only selected 5.4.2.1 > because the readme mentioned that 5.4 finally support IPv6 on Solaris. > Backwards compatibility is considered very important for the Net-SNMP project, so the latest release of the 5.4 or 5.5 branch should be fine. Regarding IPv6 support on Windows: it is easier to build Net-SNMP with IPv6 support enabled using a more recent compiler than MSVC 6. This is because more recent MSVC versions include PSDK headers with IPv6 support such that the PSDK does not have to be downloaded and installed separately. > I have run in to another interesting problem, this time when linking with > my s/w. I have done my best to ensure that the 'Zl' compiler option is set > when I compile netsnmp.lib, and my main s/w environment includes the > 'nodefaultlib:"msvcrt.lib"' directive, yet I get all manner of > multiply-defined symbols when I try to link my executable under Visual > Studio. Does this ring a bell at all? > Sorry, but I haven't encountered this issue before with the Net-SNMP workspaces -- not with MSVC 6, not with MSVC 2005 and not with MSVC 2008. Your local copies of the workspace files probably contain changes that cause these errors. Comparing the files you are working with with the original workspace files might help. Bart.
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
