Created attachment 286495 [details] ruby-1.9.2_p290-build.log In its universal binary support, ruby-1.9's configure.in removes -m32 and -m64 from CFLAGS. This breaks building a 32-bit ruby under portage-multilib. See build.log. I expect to be able to attach a tested patch which removes the RUBY_UNIVERSAL_ARCH and RUBY_DEFAULT_ARCH calls from configure.in soon.
Created attachment 286497 [details] emerge--info.txt
Created attachment 286509 [details, diff] ruby-1.9-CFLAGS-multilib.patch Applying this patch and remembering to reinstall dev-ruby/rubygems under portage-multilib produces a working 32-bit ruby installation (with one minor modification to the multilib overlay which tommy should have committed within a day) :-).
Shouldn't this be reported upstream? Also, is this patch still valid/needed for ruby 1.9.3?