| Summary: | dev-ruby/rdoc-4.0.1-r2 - ruby: no such file to load -- auto_gem (LoadError) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
| Component: | [OLD] Development | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | Skirmitch, walch.martin |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Juergen Rose
2014-01-03 09:12:32 UTC
Confirming it: >>> Emerging (1 of 1) dev-ruby/rdoc-4.0.1-r1 * rdoc-4.0.1.gem SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... * Running unpack phase for all ... * Unpacking .gem file... ... [ ok ] * Uncompressing metadata ... [ ok ] * Unpacking data.tar.gz ... [ ok ] >>> Source unpacked in /var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/work >>> Preparing source in /var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/work ... * Running prepare phase for all ... * Applying rdoc-3.0.1-bin-require.patch ... [ ok ] * Running source copy phase for ruby19 ... * Running source copy phase for ruby20 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/work ... * Running compile phase for ruby19 ... * Running compile phase for ruby20 ... * Running compile phase for all ... ruby: no such file to load -- auto_gem (LoadError) * ERROR: dev-ruby/rdoc-4.0.1-r1::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 4351: Called ruby-ng_src_compile * environment, line 4009: Called _ruby_invoke_environment 'all' 'all_ruby_compile' * environment, line 559: Called all_ruby_compile * environment, line 645: Called die * The specific snippet of code: * ruby -Ilib -S bin/rdoc || die; * * If you need support, post the output of `emerge --info '=dev-ruby/rdoc-4.0.1-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-ruby/rdoc-4.0.1-r1::gentoo'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =rdoc-4.0.1 * The complete build log is located at '/var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/temp/environment'. * Working directory: '/var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/work/all/rdoc-4.0.1' * S: '/var/tmp/portage/dev-ruby/rdoc-4.0.1-r1/work/all/rdoc-4.0.1' Which version of ruby is eselected? That was the problem, exactly, i had eselected ruby-18 without gems and that caused the problem. Before i tryed playing with ruby_targets and did a huge mess with emerge failing awefully so i didnt think it was that tho changing eselect did the trick. Would b nice to have a kind of warning in the ebuild since, at least in my case, ruby is just a dependence with which i dont mess up at all so i never figured out it was that (not like python which is way more used and common to solve problems with), its just an idea. Greetings and solved for me at least. Juergen: was this also an eselect issue for you? (In reply to Hans de Graaff from comment #4) > Juergen: was this also an eselect issue for you? I don't know, I had the issue almost four month ago. Now I have: root@impala:/root(92)# eselect ruby list Available Ruby profiles: [1] ruby19 (with Rubygems) [2] ruby20 (with Rubygems) * [3] ruby21 (with Rubygems) and rdoc-4.0.1-r2 was succesfully emerge twice in th last three mnonth: root@impala:/root(93)# genlop -t dev-ruby/rdoc | tail Sat Dec 28 20:52:15 2013 >>> dev-ruby/rdoc-4.0.1-r2 merge time: 2 minutes and 3 seconds. Thu Jan 23 11:19:35 2014 >>> dev-ruby/rdoc-4.0.1-r2 merge time: 1 minute and 37 seconds. Mon Mar 17 06:54:26 2014 >>> dev-ruby/rdoc-4.0.1-r2 merge time: 1 minute and 20 seconds. Ok, I'm going to assume this was the same issue and close this bug. |
