When I try to emerge ruby-gettext I get the following error about not being able to find fileuitls.rb. fileutils.rb is present in: /usr/lib/ruby/1.8/fileutils.rb Reproducible: Always Steps to Reproduce: 1. emerge ruby-gettext Actual Results: /var/tmp/portage/ruby-gettext-0.8.0/work/ruby-gettext-package-0.8.0/./post-setup.rb:8:in `require': No such file to load -- fileutils (LoadError) from /var/tmp/portage/ruby-gettext-0.8.0/work/ruby-gettext-package-0.8.0/./post-setup.rb:8:in `instance_eval' from setup.rb:583:in `instance_eval' from setup.rb:583:in `try_run_hook' from setup.rb:577:in `run_hook' from setup.rb:1315:in `exec_task_traverse' from setup.rb:1123:in `exec_setup' from setup.rb:883:in `exec_setup' from setup.rb:710:in `__send__' from setup.rb:710:in `invoke' from setup.rb:674:in `invoke' from setup.rb:1352 Expected Results: ruby-gettext is emerged. emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r4 i686) ================================================================= System uname: 2.6.11-gentoo-r4 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 9 2005, 06:10:37)] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.7.9-r1, 1.5, 1.8.5-r3, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -march=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -march=athlon-xp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://gentoo.mirrors.pair.com/ http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ http://gentoo.osuosl.org/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="X Xaw3d acpi acpi4linux alsa apache2 apm arts avi bash-completion berkdb bitmap-fonts cdb cdparanoia cdr crypt cups curl curlwrappers directfb dvd dvdr emacs emacs-w3 emboss encode esd exif fam fbcon fdftk flac foomaticdb fortran freetype ftp gd gdbm gif gnome gphoto2 gpm gtk gtk+ gtk2 guile imagemagick imlib jack java jpeg kde libg++ libwww mad maildir mbox mikmod motif mozilla mp3 mpeg mysql mysqli ncruses ncurses nls nocardbus nvidia oggvorbis opengl oss pam pcre pdflib perl php png posix ppds python qt quicktime readline ruby samba scanner sdl simplexml slang spell spl sqlite ssh ssl svg svga tcltk tcpd tetex tidy tiff truetype truetype-fonts type1-fonts unicode usb vhosts wmf x86 xface xml xml2 xmlrpc xmms xosd xpm xprint xv yaz zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Is this related to bug #48550? I removed the "ruby16" from the USE_RUBY="ruby16 ruby18 ruby19" line of the ruby-gettext-0.8.0 ebuild and then it compiled successfully for me. Note: Before changing the ebuild as above, the ruby18 part of the ebuild was done first on my system and then I received the same failure as Bob Paddock while trying to compile the ruby16 version. My system has fileutils.rb in /usr/lib/ruby/1.8, but not in /usr/lib/ruby/1.6
It actually needs ruby-shim18 if you have ruby16. I don't know how to express this dependency except creating virtual/ruby-1.8, but this is just in progress for the next version of portage.
Removing RUBY16 from the ebuild got it working. Thank you for your help.
should be fixed in 1.0.0 ?
