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 main.o: In function `rb_rrd_graph': main.c:(.text+0x570): undefined reference to `rrd_graph' main.o: In function `rb_rrd_xport': main.c:(.text+0x782): undefined reference to `rrd_xport' main.o: In function `rb_rrd_graphv': ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20190202-013512 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-1.32.0 * emerge -qpvO dev-ruby/rrdtool-bindings [ebuild N ] dev-ruby/rrdtool-bindings-1.7.1 USE="-graph -test" RUBY_TARGETS="ruby24 ruby25 ruby26 -ruby23"
Created attachment 563852 [details] emerge-info.txt
Created attachment 563854 [details] dev-ruby:rrdtool-bindings-1.7.1:20190205-174855.log
Created attachment 563856 [details] emerge-history.txt
Created attachment 563858 [details] environment
Created attachment 563860 [details] etc.portage.tbz2
Created attachment 563862 [details] logs.tbz2
dev-ruby/rrdtool-bindings-1.7.1 seems to have some dependency issues. It was bailing out with errors requiring rubygems on a new install however rubygems wasn't installed yet.. After emerging, I was met with the same error which I fixed by adding the 'graph' useflag to rrdtool and rrdtool-bindings which rrdtool then compiled correctly
* RUBY_PATCHES is no longer supported, use PATCHES instead Oh, that was subtle... :-/
commit 534b37d147c8259b755df3b07fd711dd5a1c2839 Author: Hans de Graaff <graaff@gentoo.org> Date: Sun Feb 19 08:42:31 2017 +0100 ruby-ng.eclass: use the default src_prepare in EAPI 6 This removes the need for inheriting eutils in EAPI 6. It also use the standard PATCHES support instead of RUBY_PATCHES, which was introduced to handle arrays on patches at the time. The default phase also handles eapply_user to handle user patches. Its users were never updated? Or did you miss some of them?
I guess it should have been an error not a warning.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6b5ce81a4bd851cc34407bec184f5d828af21142 commit 6b5ce81a4bd851cc34407bec184f5d828af21142 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-03-23 12:15:32 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-03-23 12:16:19 +0000 dev-ruby/rrdtool-bindings: EAPI=5 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Fixes: https://bugs.gentoo.org/677332 Signed-off-by: Jeroen Roovers <jer@gentoo.org> dev-ruby/rrdtool-bindings/rrdtool-bindings-1.7.1.ebuild | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
(In reply to Jeroen Roovers from comment #10) > I guess it should have been an error not a warning. Yes, in hindsight that would have been better to make this change more explicit and avoid mostly silent failure.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0d9b2338f96f7316de557542622856734251332e commit 0d9b2338f96f7316de557542622856734251332e Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2019-04-21 07:45:50 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2019-04-21 07:45:50 +0000 dev-ruby/rrdtool-bindings: EAPI=6 Bug: https://bugs.gentoo.org/677332 Signed-off-by: Hans de Graaff <graaff@gentoo.org> Package-Manager: Portage-2.3.62, Repoman-2.3.11 .../rrdtool-bindings-1.7.1-r1.ebuild | 60 ++++++++++++++++++++++ 1 file changed, 60 insertions(+)
