Since gcc-4.3.3 -D_FORTIFY_SOURCE=2 is set implicitly. This causes seamonkey-1.1.14 to fail with a buffer overflow already during emerge (see below). A similar problem was there with earlier firefox-versions, but apparently firefox has been fixed in this respect: Running seamonkey-rebuild-databases.pl *** buffer overflow detected ***: /usr/lib/seamonkey/regxpcom terminated >>> Regenerating /etc/ld.so.cache... >>> Original instance of package unmerged safely. Running seamonkey-rebuild-databases.pl *** buffer overflow detected ***: /usr/lib/seamonkey/regxpcom terminated >>> Regenerating /etc/ld.so.cache...
Hrm...so you say that building seamonkey with gcc-4.3.3 fails, no? It doesn't here, and i don't see FORTIFY during the build. Portage 2.1.6.4 (default/linux/amd64/2008.0/desktop, gcc-4.3.3, glibc-2.9_p20081201-r1, 2.6.16.16 x86_64) ================================================================= System uname: Linux-2.6.16.16-x86_64-AMD_Athlon-tm-_64_Processor_3200+-with-glibc2.2.5 Timestamp of tree: Sat, 14 Feb 2009 11:15:02 +0000 app-shells/bash: 3.2_p39 dev-lang/python: 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.7.9-r1, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64"
Nvm, was able to reproduce now.
Fixed in 1.1.4's 0.1 patchset, please sync in an hour or so and try again, if it works, please close the bug.
Compiled and started successfully on x86 and amd64