emerge xmessage, or any deep update of xorg-server, will return x11-apps/xmessage-1.0.2-r1 dying with an emake failed message in the error report. Reproducible: Always Steps to Reproduce: 1. Run 'emerge xmessage' or 'emerge -auvDN xorg server' 2. Upon grabbing the source for xmessage, the emerge fails. Actual Results: Emerge failed with a die message of "emake failed". Expected Results: Successful emerge. make[1]: Leaving directory `/var/tmp/portage/x11-apps/xmessage-1.0.2-r1/work/xmessage-1.0.2' make: *** [all] Error 2 * * ERROR: x11-apps/xmessage-1.0.2-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3124: Called x-modular_src_compile * environment, line 3909: Called x-modular_src_make * environment, line 3949: Called die * The specific snippet of code: * emake || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-apps/xmessage-1.0.2-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-apps/xmessage-1.0.2-r1/temp/environment'. *
*** Bug 286596 has been marked as a duplicate of this bug. ***
I just realized that I was building with sys-devel/gcc-4.1.2, which is marked as Deprecated in Portage. Updating GCC now, will try to re-emerge xmessage after this update to see if the bug is still reproducible.
Reopen if it still fails. If so, provide emerge --info and the build.log (see the end of the error message).