laptop root # emerge -U --deep world >>> --upgradeonly implies --update... adding --update to options. Calculating world dependencies ...done! >>> emerge (1 of 2) net-analyzer/net-snmp-5.0.6-r1 to / >>> md5 src_uri ;-) net-snmp-5.0.6.tar.gz >>> Unpacking source... >>> Unpacking net-snmp-5.0.6.tar.gz to /var/tmp/portage/net-snmp-5.0.6-r1/work /usr/sbin/ebuild.sh: line 26: /usr/portage/net-analyzer/net-snmp/files/net-snmp-5.0.6-r1-gentoo.diff: No such file or directory >>> Source unpacked. ssl tcpd creating cache ./config.cache [...snip...] mv -f agentx/.libs/agentx_config.lo agentx/agentx_config.lo make[2]: Leaving directory `/var/tmp/portage/net-snmp-5.0.6-r1/work/net-snmp-5.0.6/agent/mibgroup' /bin/sh ../libtool --mode=compile gcc -march=pentium3 -O3 -pipe -Dlinux -I../include -I../include -I.. -I./.. -I./../snmplib -I. -I. -I./mibgroup -Imibgroup -c -o snmp_agent.lo snmp_agent.c mkdir .libs gcc -march=pentium3 -O3 -pipe -Dlinux -I../include -I../include -I.. -I./.. -I./../snmplib -I. -I. -I./mibgroup -Imibgroup -c snmp_agent.c -fPIC -DPIC -o .libs/snmp_agent.lo snmp_agent.c:74: `LOG_INFO' undeclared here (not in a function) snmp_agent.c:75: `LOG_WARNING' undeclared here (not in a function) make[1]: *** [snmp_agent.lo] Error 1 make[1]: Leaving directory `/var/tmp/portage/net-snmp-5.0.6-r1/work/net-snmp-5.0.6/agent' make: *** [subdirs] Error 1 !!! ERROR: net-analyzer/net-snmp-5.0.6-r1 failed. !!! Function src_compile, Line 60, Exitcode 2 !!! compile problem --- Thanks for your work!
Believed fixed in CVS.
I had the same problem with 5.0.6-r1. But the net-snmp-5.0.8 ebuild (dated 28 May) that exists does not have this issue for me. Is there any reason that the 5.0.8 ebuild cannot be marked stable?
Confirmed fixed. As for 5.0.8, the issue that is patched in 5.0.6 is apparently no longer needed in 5.0.8, so even though the patch failed, it built OK. I took the line out to patch in the 5.0.8 ebuild. As to why it's still masked, it probably needs more testing. I am not the normal snmp maintainer, but happened to see the bug reported in IRC.
*** Bug 21724 has been marked as a duplicate of this bug. ***
