I just did a clean Gentoo 2006.1 install in a chroot. First I did emerge -uD world once. Then emerge -a rails. The following ebuilds installed fine: dev-ruby/ruby-config-0.3.1 dev-lang/ruby-1.8.5_p2 But dev-ruby/rubygems-0.8.11-r5 failed with: >>> Emerging (1 of 11) dev-ruby/rubygems-0.8.11-r5 to / * rubygems-0.8.11.tgz MD5 ;-) ... [ ok ] * rubygems-0.8.11.tgz RMD160 ;-) ... [ ok ] * rubygems-0.8.11.tgz SHA1 ;-) ... [ ok ] * rubygems-0.8.11.tgz SHA256 ;-) ... [ ok ] * rubygems-0.8.11.tgz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking rubygems-0.8.11.tgz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking rubygems-0.8.11.tgz to /var/tmp/portage/rubygems-0.8.11-r5/work * Applying no_post_install.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/rubygems-0.8.11-r5/work/rubygems-0.8.11 ... >>> Source compiled. >>> Test phase [not enabled]: dev-ruby/rubygems-0.8.11-r5 >>> Install rubygems-0.8.11-r5 into /var/tmp/portage/rubygems-0.8.11-r5/image/ category dev-ruby /usr/bin/ruby: no such file to load -- auto_gem (LoadError) /usr/bin/ruby: no such file to load -- auto_gem (LoadError) !!! ERROR: dev-ruby/rubygems-0.8.11-r5 failed. Call stack: ebuild.sh, line 1546: Called dyn_install ebuild.sh, line 1020: Called src_install rubygems-0.8.11-r5.ebuild, line 29: Called ruby_src_install ruby.eclass, line 182: Called ruby_einstall ruby.eclass, line 134: Called die !!! setup.rb config failed !!! If you need support, post the topmost build error, and the call stack if relevant. make.conf: CFLAGS="-O3 -march=i686 -pipe -ffast-math -fomit-frame-pointer -mmmx" CHOST="i686-pc-linux-gnu" CXXFLAGS="${CFLAGS}" FEATURES="parallel-fetch" PORTDIR_OVERLAY="/usr/local/portage" USE="-gpm fastcgi mysql" I tried env-update && source /etc/profile, but it didn't help. # ruby-config -c * Your current profile refers to ruby18. # irb /usr/bin/ruby18: no such file to load -- auto_gem (LoadError)
*** This bug has been marked as a duplicate of 143632 ***
(In reply to comment #1) > > *** This bug has been marked as a duplicate of 143632 *** > Erm, how is this duplicate of that. I'm using different version of ruby and rubygems. The error message is different and I already have ruby installed. 'ruby-config ruby18' does not help. There is no 'emerge --config ruby' option. So what am I supposed to do? Some discussion can be found here: http://www.mail-archive.com/gentoo-alt%40lists.gentoo.org/msg01122.html I've tested those. Any of those advices didn't help this time. Here's some more output: # ls -la /usr/bin/ruby lrwxrwxrwx 1 root root 6 2006-12-18 14:29 /usr/bin/ruby -> ruby18 # emerge --info Portage 2.1.1-r2 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.17-reiser4-r7 i686) ================================================================= System uname: 2.6.17-reiser4-r7 i686 AMD Athlon(TM) XP 2400+ Gentoo Base System version 1.12.6 Last Sync: Mon, 18 Dec 2006 01:00:02 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=i686 -pipe -ffast-math -fomit-frame-pointer -mmmx" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O3 -march=i686 -pipe -ffast-math -fomit-frame-pointer -mmmx" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="fi_FI.UTF-8" LC_ALL="fi_FI.UTF-8" LINGUAS="fi" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 berkdb bitmap-fonts cli cracklib crypt cups dlloader dri elibc_glibc fastcgi fortran gdbm iconv input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog kernel_linux libg++ linguas_fi mysql ncurses nls nptl nptlonly pam pcre perl ppds pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts udev unicode userland_GNU video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_i740 video_cards_i810 video_cards_imstt video_cards_mga video_cards_neomagic video_cards_nsc video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_vga video_cards_via video_cards_vmware video_cards_voodoo xorg zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Ok, found it. RUBYOPT="" emerge rubygems fixed it. Got some help from here: http://forums.gentoo.org/viewtopic.php?t=470375 I suppose there is something we can do to prevent this later on?
This bug hits me several times :( "emerge -C rubygems;emerge -1 rubygems" can trigger it. Perhaps we should unset RUBYOPT (or filter out -rauto_gem in rubygems ebuild (or ruby.eclass maybe?).
Tis fine me with, if someone wants to undertake and test it.
new rubygems-0.8.11-r5 and 0.9.0-r2 should fix it
*** Bug 234475 has been marked as a duplicate of this bug. ***