Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 305775 - [dev-ruby/rubygems-1.3.5-r3] build failed with exception
Summary: [dev-ruby/rubygems-1.3.5-r3] build failed with exception
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-18 17:26 UTC by Gabor Garami
Modified: 2010-04-06 09:06 UTC (History)
0 users

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


Attachments
emerge --info (emerge-info-v.txt,11.72 KB, text/plain)
2010-02-18 17:27 UTC, Gabor Garami
Details
build log (build.log,3.37 KB, text/plain)
2010-02-18 17:27 UTC, Gabor Garami
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Garami 2010-02-18 17:26:17 UTC
Under emerging rubygems, the build process fails with an exception "no such file to load -- gentoo (LoadError)" - maybe gentoo-related stuff not added. On my system, RUBY_TARGET="ruby18 jruby" (see emerge --info output in attachment).


Reproducible: Always

Steps to Reproduce:
1. Set RUBY_TARGETS="ruby18 jruby" in make.conf
2. keyword ~amd64 to dev-ruby/rubygems 
3. emerge this package

Actual Results:  
Exception in thread "main" :1: no such file to load -- gentoo (LoadError)
	...internal jruby stack elided...
	from (unknown).(unknown)(:1)
Exception in thread "main" :1: no such file to load -- gentoo (LoadError)
	...internal jruby stack elided...
	from (unknown).(unknown)(:1)


Expected Results:  
Correct build & merge process
Comment 1 Gabor Garami 2010-02-18 17:27:19 UTC
Created attachment 220191 [details]
emerge --info
Comment 2 Gabor Garami 2010-02-18 17:27:42 UTC
Created attachment 220193 [details]
build log
Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev 2010-02-19 12:23:09 UTC
This problem is due to upgrading from an older jruby installation without re-sourcing the profile (and thus without cleaning up the enviornment).

Unfortunately, we have no way to handle that for now :/
Comment 4 Gabor Garami 2010-02-25 09:04:12 UTC
(In reply to comment #3)
> This problem is due to upgrading from an older jruby installation without
> re-sourcing the profile (and thus without cleaning up the enviornment).
> 
> Unfortunately, we have no way to handle that for now :/
> 

But, it can be a workaround, if pkg_setup die if older jruby installation is on system.
Comment 5 Vlastimil Babka (Caster) (RETIRED) gentoo-dev 2010-04-06 09:06:15 UTC
Note that source /etc/profile didn't work here, had to relogin (reconnect via ssh).