630708 – app-text/ronn fails to build -- "fatal: the 'hpricot' library is required"

Bug 630708 - app-text/ronn fails to build -- "fatal: the 'hpricot' library is required"

Summary: app-text/ronn fails to build -- "fatal: the 'hpricot' library is required"

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Ruby Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2017-09-11 17:43 UTC by Markus Walter
Modified:	2017-09-12 08:49 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
build log (ronn-0.7.3-r3:20170911-065837.log,2.41 KB, text/x-log) 2017-09-11 17:43 UTC, Markus Walter	Details
emerge --info (info.txt,7.82 KB, text/plain) 2017-09-11 17:43 UTC, Markus Walter	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Markus Walter 2017-09-11 17:43:35 UTC

Created attachment 494032 [details]
build log

On my ~amd64 machine I see the following mysterious error when building ronn.

* Running compile phase for all ...
fatal: the 'hpricot' library is required (gem install hpricot)

This is besides dev-ruby/hpricot being installed. I did check whether it has the same ruby slots active, but everything seems to be in order. I also did several rebuilds of hpricot, but to no avail. Any ideas?

Comment 1 Markus Walter 2017-09-11 17:43:50 UTC

Created attachment 494034 [details]
emerge --info

Comment 2 Hans de Graaff gentoo-dev

2017-09-12 05:26:27 UTC

It looks like you might have an unsupported version of ruby eselected (either ruby 2.1 or ruby2.4).

Comment 3 Markus Walter 2017-09-12 08:49:12 UTC

(In reply to Hans de Graaff from comment #2)
> It looks like you might have an unsupported version of ruby eselected
> (either ruby 2.1 or ruby2.4).

Indeed I had ruby2.4 eselected and switching to ruby2.3 solved the problem. This is however pretty non-obvious to diagnose so a more helpful error detection may prevent others from being as confused as I was.