Bug 638898 – dev-ruby/nokogumbo-1.4.13 : * (no error message)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2017-11-26 15:06:57 UTC]

 * ERROR: dev-ruby/nokogumbo-1.4.13::gentoo failed (configure phase):
 *   (no error message)
 * 

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 13.0-no-multilib_libressl_20171120-180602

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python3.6 (fallback)
  [3]   python2.7 (fallback)
  [4]   pypy3 (fallback)
Available Ruby profiles:
  [1]   ruby22 (with Rubygems) *
java-config:
The following VMs are available for generation-2:


emerge -qpv dev-ruby/nokogumbo
[ebuild  N    ] dev-ruby/nokogumbo-1.4.13  USE="-doc {-test}" RUBY_TARGETS="ruby22 -ruby23 -ruby24"

[Comment 1 Toralf Förster 2017-11-26 15:07:00 UTC]

Created attachment 506728 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-11-26 15:07:03 UTC]

Created attachment 506730 [details]
dev-ruby:nokogumbo-1.4.13:20171126-124013.log

[Comment 3 Toralf Förster 2017-11-26 15:07:06 UTC]

Created attachment 506732 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-11-26 15:07:10 UTC]

Created attachment 506734 [details]
environment

[Comment 5 Toralf Förster 2017-11-26 15:07:13 UTC]

Created attachment 506736 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2017-11-26 15:07:16 UTC]

Created attachment 506738 [details]
logs.tbz2

[Comment 7 Hans de Graaff 2018-02-06 06:25:35 UTC]

I can't reproduce this.

Perhaps this is fixed for you with the newer nokogumbo 1.5.0 which I've just added?

[Comment 8 Toralf Förster 2018-02-06 18:27:44 UTC]

yep, fixed here (even 1.4.43 builds fine here today)