If you try to emerge the ruby with the latest patches (dev-lang/ruby-1.8.6_p230), you will get the following error: ERROR: dev-lang/ruby-1.8.6_p230 failed: * econf failed * * Call stack: * ebuild.sh: 49: <call src_compile> * environment:3196: <call econf '--program-suffix=18' '--enable-shared' '--disable-socks' '--disable-install-doc' '--disable-pthread' '--enable-ipv6' '--disable-debug' '--without-dbm' '--without-gdbm' '--with-openssl' '--without-tk' '--with-sitedir=/Users/mh/Library/Gentoo/usr/lib/ruby/site_ruby'> * ebuild.sh: 538: die "econf failed" Suprisingly the build log is empty. If i try to redo the configure by hand, I'll get a warning that some options are not supported: configure: WARNING: Unrecognized options: --disable-socks, --enable-ipv6, --disable-debug, --without-dbm, --without-gdbm, --with-openssl, --without-tk Reproducible: Always Steps to Reproduce:
hmmm,here it configures fine, but fails during make...
ehm, the fail is due to a h0rkened portage I use.
it installed just fine here for me... >>> dev-lang/ruby-1.8.6_p230 merged.
It could be the same problem for me. I had problems earlier emerging the newest portage version. Just I'm doing a --sync to see if there's an added portage version to reemerge portage and to see whether the problem is gone then.
what portage version do you have installed? If it's too new you're bitten by a mistake I made. Current code in svn is horribly broken, with the only remedy to bootstrap portage again in your prefix.
Well, current version of portage is portage-2.2.00.10815 which works just fine after doing the following: ebuild /Volumes/Alesia/Gentoo/usr/portage/sys-apps/portage/portage-2.2.00.10815.ebuild merge emerge portage before that it would not move from .10788 to .10815 . After doing the ebuild merge and the reemerge of portage ruby itself builds again as well, still complaining about the unknown switches though.
