I know it's an upstream bug, but I hope someone can actually push it upstream, as I don't really want to submit more bugs to them considering the way I've been ignored in the past, and maybe we can at least try to solve this from a Gentoo side in the mean time. The libnetsnmp.so and libsnmp.so libraries are just the same library, they are both built from the same object files, and they both have the same code: flame@enterprise amarok-1.4.8 % objdump -s -j .text /usr/lib/libnetsnmp.so | tail -n +5 | cut -d ' ' -f 3- | md5sum 2d4d55b865389b7b8bc37d2bc86f8fb0 - flame@enterprise amarok-1.4.8 % objdump -s -j .text /usr/lib/libsnmp.so | tail -n +5 | cut -d ' ' -f 3- | md5sum 2d4d55b865389b7b8bc37d2bc86f8fb0 -
Actually this is not a bug but feature which is enabled/disabled with --enable-ucd-snmp-compatibility ./configure switch. Probably now it is good time to consider ucd-snmp package completely dead and drop compatibility. I'll leave 5.4 branch as it is now but will change this for 5.5 branch...
I sincerely think they made the compatibility wrong, they should have used either a linker script to use the other library name or just a lightweight layer to get the other one used...
Okay I disabled it with 5.7.2_rc1 and will run the tinderbox to make sure it doesn't break anything.
