Mozilla configure does some funny exceptions check and fails. It therefore adds -fno-handle-exceptions flag instead of -fno-exceptions. Patch attached.
Created attachment 186444 [details] build.log with wrong result for C++ exceptions check
Created attachment 186446 [details, diff] clean and fix C++ exceptions check
Hmm, run configure manually selects -fno-exceptions, run via emerge it selects -fno-handle-exceptions. Let's see.
Created attachment 186455 [details, diff] remove exceptions check and enforce -fno-exceptions ... since noone uses g++ <2.8 nowadays?
(In reply to comment #4) > Created an attachment (id=186455) [edit] > remove exceptions check and enforce -fno-exceptions > > ... since noone uses g++ <2.8 nowadays? > actually the check is fine as mozilla tries to maintain backward compatibility as long as possible.
The idea of the check is fine, yes. The implementation of the check adds the wrong flag. ;) See comment 0. Looking at http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/ there is the version 2.95 the oldest. Now with that, the check is simply superfluous. Please tell me about a box that uses <gcc-2.8 to build xulrunner. :) I wonder if that versions are even able to build it. ;)
Please open a bug upstream. If they decide they want to fix it we will fix it in gentoo. There is nothing that is gonna be broken by the exception check.
