*** --with-snmp-lib=DIR *** configure: error: SNMP checks failed !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-analyzer/mbrowse-0.4.3-r1/work/mbrowse-0.4.3/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop_test_20190313-190226 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy3 (fallback) Available Rust versions: [1] rust-bin-1.32.0 * [2] rust-1.32.0 java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.10.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO net-analyzer/mbrowse [ebuild N ] net-analyzer/mbrowse-0.4.3-r1
Created attachment 569448 [details] emerge-info.txt
Created attachment 569450 [details] emerge-history.txt
Created attachment 569452 [details] environment
Created attachment 569454 [details] etc.portage.tbz2
Created attachment 569456 [details] logs.tbz2
Created attachment 569458 [details] net-analyzer:mbrowse-0.4.3-r1:20190317-065425.log
Created attachment 569460 [details] temp.tbz2
*** Bug 688028 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8fa1939e9863520bc28af945c9e0a1414ab4c2bb commit 8fa1939e9863520bc28af945c9e0a1414ab4c2bb Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-06-20 08:01:05 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-06-20 08:01:46 +0000 net-analyzer/mbrowse: Specify SNMP LIBDIR in configure call Package-Manager: Portage-2.3.67, Repoman-2.3.14 Bug: https://bugs.gentoo.org/680686 Signed-off-by: Jeroen Roovers <jer@gentoo.org> net-analyzer/mbrowse/mbrowse-0.4.3-r1.ebuild | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
Somehow this exact same problem just returned with the lastest SNMP update. Does anybody know more about it? I can provide logs, but it's exactly the same issue all over again.
(In reply to Richard H. from comment #10) > Somehow this exact same problem just returned with the lastest SNMP update. > Does anybody know more about it? I can provide logs, but it's exactly the > same issue all over again. I think logs would help to figure out what component is outdated or what else is going on.