>>>>> On Thu, 19 May 2011 14:57:57 +0000, "Rusk, Mark" <mark.r...@hp.com> said:
RM> 1)When dlmod modules (x86_64) are built with net-snmp-5.5 (or earlier) RM> are loaded into a net-snmp-5.6.1 snmpd the typedefs for oid are in RM> conflict. You end up trying to register OIDS 1.0.3.0.6.0.1.0.4.0.*, RM> instead of 1.3.6.1.4.* Right, that's because 5.6.1 changed in an incompatible way (IE, the tyepdef for the oid changed to a 4 byte datatype from an 8, so the above problem makes perfect sense). But supposedly the datatype changed to a int *because* it broke something else. That's what I need to figure out: what is broken on an 64-bit architecture when the OID is typedefed as a long (which it historically has for years and years). -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
