x86_64-pc-linux-gnu-gcc -shared -o RRD.so main.o -L. -L/usr/lib64 -L/src/.libs -L. -Wl,-O1 -Wl,--as-needed -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,--no-undefined -Wl,--rpath -Wl,/lib -Wl,-O1 -Wl,--as-needed -Wl,--compress-debug-sections=zlib -lruby24 -lrrd -lpthread -lgmp -ldl -lcrypt -lm -lc /usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../../x86_64-pc-linux-gnu/bin/ld: main.o: in function `rb_rrd_graph': main.c:(.text+0x563): undefined reference to `rrd_graph' /usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../../x86_64-pc-linux-gnu/bin/ld: main.o: in function `rb_rrd_xport': main.c:(.text+0x774): undefined reference to `rrd_xport' /usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../../x86_64-pc-linux-gnu/bin/ld: main.o: in function `rb_rrd_graphv': ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-libressl-20190717-053737 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.36.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] 2) JamVM JDK 2.0.0 [jamvm] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm [2] jamvm emerge -qpvO dev-ruby/rrdtool-bindings [ebuild N ] dev-ruby/rrdtool-bindings-1.7.2 USE="-graph -test" RUBY_TARGETS="ruby24 ruby25 -ruby26"
Created attachment 583784 [details] emerge-info.txt
Created attachment 583786 [details] dev-ruby:rrdtool-bindings-1.7.2:20190720-184420.log
Created attachment 583788 [details] emerge-history.txt
Created attachment 583790 [details] environment
Created attachment 583792 [details] etc.portage.tbz2
Created attachment 583794 [details] logs.tbz2
net-analyzer/rrdtool needs USE=graph for the rrdtool-bindings to succeed. This is covered in the DEPEND of the ebuild, but it looks like rrdtool was emerged without it. I'm not sure if the tinderbox automatically handles this correctly.
it's only in RDEPEND, maybe that is the cause?
(In reply to Rolf Eike Beer from comment #8) > it's only in RDEPEND, maybe that is the cause? Good catch.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6d4208982d86c95b77e68f9da8126f6417b1ef85 commit 6d4208982d86c95b77e68f9da8126f6417b1ef85 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-09-14 08:35:42 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-09-14 08:40:39 +0000 dev-ruby/rrdtool-bindings: DEPEND on net-analyzer/rrdtool Package-Manager: Portage-2.3.76, Repoman-2.3.17 Bug: https://bugs.gentoo.org/690318 Signed-off-by: Jeroen Roovers <jer@gentoo.org> .../rrdtool-bindings/rrdtool-bindings-1.6.0.ebuild | 1 + .../rrdtool-bindings/rrdtool-bindings-1.7.0.ebuild | 60 ---------------------- .../rrdtool-bindings-1.7.1-r1.ebuild | 1 + .../rrdtool-bindings/rrdtool-bindings-1.7.1.ebuild | 59 --------------------- .../rrdtool-bindings/rrdtool-bindings-1.7.2.ebuild | 1 + 5 files changed, 3 insertions(+), 119 deletions(-)
Presumed fixed.
