Hi Shane.
I did some digging also and found the following message from Dave which says that the patch was not applied to the 5.0 line:
http://sourceforge.net/mailarchive/message.php?msg_id=9074365
You could try the patch yourself by modifying the SNMP.xs file and changing the line that contains:
(void)PerlIO_fprintf(PerlIO_stderr(), otherargs);
to:
void)PerlIO_printf otherargs;
If you would like to stick with the RedHat RPMs, you should be able to download the SRPM (source RPM), modify the file, re-create a new set of RPMs, and then install the RPM. I can't recall the exact steps right now as it's been a while since I built an RPM. Hopefully someone else can help with it.
What did you do to get the error to appear? Was it just a make test? I tried on my system and it didn't have a problem with that function.
Alex
Shane Dawalt wrote:
I found William R. Buckley's discussion of this problem from July 2004. It would appear the solution is to move to a version greater than 5.0 according to a reply. But I'm back to the same problem - there is only RH9 and FC2 RPMs available. Does anyone know what kind of dark arts are required to create a local RPM? Is it safe to build and install a package without an RPM? This is the first time I've dealt with RPMs and I'm uncertain what works and what doesn't. Any pointers?
Shane
Shane Dawalt wrote:
I have Red Hat Enterprise (2.4.21-27.0.2.ELsmp) installed. The latest NetSNMP RPM at RH is 5.0.9 which is installed. But for whatever reason the NetSNMP RPM didn't have the perl modules bundled with it. The perlmod RPMs on SourceForge are for RH9 and I think 2.4.* is RH7.3. I tried building the perl tree from a 5.0.9 tarball, but when I tested it, a failure occurred:
Can't load '../blib/arch/auto/SNMP/SNMP.so' for module SNMP: ../blib/arch/auto/SNMP/SNMP.so: undefined symbol: PerlIO_fprintf at /usr/lib64/perl5/5.8.0/x86_64-linux-thread-multi/DynaLoader.pm line 229.
at ../blib/lib/NetSNMP/OID.pm line 19
What could be reasons for the inability to find PerlIO_fprintf?? If I'm interpreting this correctly, SNMP.so was actually found by the loader, so it's not one of the more troublesome shared library loading issues ... as far as SNMP.so is concerned anyway.
Shane
------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
