When compiling packages for another machine on OTHERHOST THEUSER needs to rely on the fact that those packages do not autoconfigure against the specific configuration resident on OTHERHOST, but try as best as they can to obey configuration THEUSER set up in make.conf, make.defaults, etc. Autoconfiguration against the specific setup of the build machine is done when building xorg-server ebuild which is evil. configure of xorg-server runs a test MMX_CAPABLE to decide wheter to enable mmx or not. This is fatal when building the X server for a box that does not support mmx (or to be more specific in my case: a box with a cpu that fails on mmx runtime-detection; e.g. caught signal 4 is thrown with an error in xf86SigHandler on a cyrix 486 target machine). xorg-server should honor the mmx useflag for sake of consistency with the gentoo ebuild system and for overall clarity ;-) A quick hack to enable just this is to copy xorg-server-....ebuild to a portage overlay, add mmx to IUSE of the ebuild, add ${use_enable mmx} to CONFIGURE_OPTIONS and add the following patch to the PATCHES variable and to the files directory of the ebuild: cat > lousy.patch <<EOF *** configure.ac 2006-12-04 05:32:48.000000000 +0100 --- configure.ac.patched 2006-12-04 05:56:16.000000000 +0100 *************** *** 279,283 **** fi AC_MSG_RESULT([$mmx_capable]) ! AM_CONDITIONAL(MMX_CAPABLE, [test "x$mmx_capable" = xyes]) --- 279,283 ---- fi AC_MSG_RESULT([$mmx_capable]) ! AM_CONDITIONAL(MMX_CAPABLE, [test "x$enable_mmx" = xmmx]) EOF
I agree that the autoconfig stuff is icky, but we won't put the patch in here without upstream endorsing it first. You're of course welcome to maintain it in your overlay until then. Please file a bug at https://bugs.freedesktop.org and request that mmx be made configurable. Paste the link here when you've done so. Thanks!
