Summary: | Kahakai 0.6.2 fails to find ruby during econf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Diers <martin> |
Component: | Current packages | Assignee: | Desktop WM Team (OBSOLETE) <desktop-wm+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | estoycon, ruby |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge log of latest attempt |
Description
Martin Diers
2004-02-11 11:06:46 UTC
Update to the above. I probably misunderstand the purpose of the use-enable function in builds. Furthermore, I discovered that I do indeed have ruby installed, though I forgot about this. That said, I changed the Summary of this bug to reflect this fact. When I try to merge, though I do indeed have the lastest stable build of ruby installed (1.8.0) the build fails to find it. Please give us the exact version of ruby you have (ruby-1.8.0.ebuild is gone from Portage tree atm) and the output of `ls -l /usr/bin/ruby*`. Also, the output of `emerge info` would be nice. Created attachment 25545 [details]
emerge log of latest attempt
I have version 1.8.0-r1 of Ruby installed.
The attached log is my emerge attempt, with the following command:
USE="ruby" ACCEPT_KEYWORDS="~x86" emerge -v kahakai
I remerged ruby and then remerged kahakai. Now it works. Changing status of bug to INVALID. |