--curdir --ruby=/usr/bin/ruby21 * ERROR: dev-ruby/ruby-gtk2-3.1.1::gentoo failed (configure phase): * extconf.rb failed * * Call stack: ----------------------------------------------------------------- This is an unstable amd64 chroot image (named plasma-systemd_20170420-191853) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] jython2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) [2] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.9 [icedtea-7] *) IcedTea JDK 7.2.6.9 [icedtea-bin-7] 3) IcedTea JDK 3.3.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-7 [2] icedtea-bin-7 system-vm [3] icedtea-bin-8
Created attachment 470976 [details] emerge-info.txt
Created attachment 470978 [details] dev-ruby:ruby-gtk2-3.1.1:20170426-201500.log
Created attachment 470980 [details] emerge-history.txt
Created attachment 470982 [details] environment
Created attachment 470984 [details] etc.portage.tbz2
Fixed upstream in version >=3.1.2, problem is caused by >=dev-ruby/pkg-config-1.1.9 Workaround: downgrade dev-ruby/pkg-config to 1.1.7 Reference: https://github.com/ruby-gnome2/ruby-gnome2/issues/1018 https://github.com/ruby-gnome2/ruby-gnome2/commit/14f9ef12fb71d4316975721956d15dc0747812e7
I confirm that downgrading dev-ruby/pkg-config makes it build. Thanks Marco!
workaround(2) sudo ln -s /usr/include/gtk-2.0/gdk /usr/include/gdk Quoted from below [Arch Linuxにmikutterをインストールする - htlsne’s blog](http://htlsne.hatenablog.com/entry/2017/05/03/115836)
(In reply to Marco Genasci from comment #6) > Fixed upstream in version >=3.1.2, problem is caused by I added 3.1.3 to the tree as a test, but it doesn't appear to have fixed the issue...
(In reply to Rick Farina (Zero_Chaos) from comment #9) > I added 3.1.3 to the tree as a test, but it doesn't appear to have fixed the > issue... Strange the patch [1] seems applied from 3.1.2 version [1] https://github.com/ruby-gnome2/ruby-gnome2/commit/14f9ef12fb71d4316975721956d15dc0747812e7
Ok I tried 3.1.3 but now some packages (i.e. dev-ruby/ruby-glib2-3.1.3) fails with error: /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- native-package-installer (LoadError) from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /var/tmp/portage/dev-ruby/ruby-glib2-3.1.3/work/ruby22/ruby-gnome2-all-3.1.3/glib2/lib/mkmf-gnome2.rb:16:in `<top (required)>' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /var/tmp/portage/dev-ruby/ruby-glib2-3.1.3/work/ruby22/ruby-gnome2-all-3.1.3/glib2/ext/glib2/extconf.rb:15:in `<main>' This probably caused by this modification (see NEWS file) * Extracted native package installer code as native-package-installer [1] gem. [1] https://github.com/ruby-gnome2/native-package-installer
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0cdb994d82ec4f3dd046c6c5d0e675b63922f0ee commit 0cdb994d82ec4f3dd046c6c5d0e675b63922f0ee Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2018-07-06 09:30:00 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2018-07-07 06:14:10 +0000 dev-ruby/ruby-gtk2: fix build issue Explicitly add gtk-2.0 include path. This should be fixed more comprehensively in later versions of ruby-gtk2. Closes: https://bugs.gentoo.org/616682 Package-Manager: Portage-2.3.40, Repoman-2.3.9 dev-ruby/ruby-gtk2/ruby-gtk2-3.1.1.ebuild | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)