Noticed while trying to emerge kOffice after --syncing on Jun 25, 2006, @06:06CST according to surveying /usr/portage for most recent wide-spread modification times. compiling Win32API compiling bigdecimal make[1]: Entering directory `/var/tmp/portage/ruby-1.8.4.20060529/work/ruby/ext/bigdecimal' Makefile:144: *** missing separator. Stop. make[1]: Leaving directory `/var/tmp/portage/ruby-1.8.4.20060529/work/ruby/ext/bigdecimal' make: *** [all] Error 1 Obviously this was an ACCEPT_KEYWORDS=~amd64 build attempt. Retrying with ~amd64 disabled, so I pulled in ruby-1.8.4-r1 I had the same error in the same directory on the same file (Makefile, missing seperator) though with a slightly different offset it referenced the same actual line. Searching for the bug on-line, I found the following two links on an english-language ruby_talk mailing list archive hosted out of Japan: Someone having the same error as I am: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/193011 Final solution to the problem mentioned (rolling back to autoconf-2.94) and someone pointing out it's most likely a regression error in autoconf-2.95: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/193168 Per these two posts, I do not believe this is an arch-specific bug so I am not marking it AMD64-specific. Unfortunately, autoconf-2.94 is no longer in Portage, only 2.95 and 2.13 are. But currently, autoconf-2.95d is specifically NOT able to be used to compile Ruby 1.8.4.
I've masked autoconf 2.59d already yesterday, as this is not the first bug. You can read more about it at http://farragut.flameeyes.is-a-geek.org/articles/2006/06/25/the-autoconf-debacle . Anyway, I'll try to fix it ASAP.
Okay I have a working patch, but Caleb just added 1.8.5_pre1, need to find if it's still needed.
Good way to waste time, mine :) 1.8.5_pre1 works out of the box.
*** Bug 141381 has been marked as a duplicate of this bug. ***
*** Bug 142914 has been marked as a duplicate of this bug. ***
*** Bug 143896 has been marked as a duplicate of this bug. ***
*** Bug 145194 has been marked as a duplicate of this bug. ***
