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.

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?

Cheers,
Ron

-- 

From: Bart Van Assche [mailto:[email protected]] 
Sent: May 3, 2010 3:01 PM
To: Ron Bets
Cc: Net SNMP Coders ([email protected])
Subject: Re: Problems building 5.2.4.1 with IPv6 support on Windows

On Mon, May 3, 2010 at 3:45 PM, Ron Bets <[email protected]> wrote:
Thanks once again.  When I added 'gdi32.lib' to the linker, snmpwalk linked 
fine.  Based on your response, I looked at the generated makefile for the 
OpenSSL build, and sure enough gdi32.lib was there.

It would still be nice to understand why the command line build doesn't work.  
Still, I think I might be able to proceed with the rest of my task now.  We 
have an old legacy product that used link with an old version of OpenSSL 
(0.9.8b) and NetSnmp (5.2.2), and it has fallen on me to update both libraries 
and make corresponding changes, if any, to our s/w, including enabling IPv6 
transport.  Hopefully I won't run in to similar problems when I do the Solaris 
(SPRO) and Linux builds ;-)

One way to make sure that MSVC 6 uses the PSDK headers during a batch build is 
to start cmd.exe and to run the following commands:

cd win32
"C:\Program Files\Microsoft Visual Studio\vc98\Bin\VCVARS32.BAT"
set INCLUDE="C:\Program Files\Microsoft Platform SDK\Include;%INCLUDE%"
build.bat

Note: apparently the V5.4 source tree doesn't build with these instructions. 
I'm still looking into this.

Bart.

------------------------------------------------------------------------------
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to