Error from the build.log: /usr/lib/gcc/i686-pc-linux-gnu/4.5.3/../../../../i686-pc-linux-gnu/bin/ld: BFD (GNU Binutils) 2.21.1 internal error, aborting at /var/tmp/portage/sys-devel/binutils-2.21.1-r1/work/binutils-2.21.1/bfd/merge.c line 877 in _bfd_merged_section_offset
Created attachment 319330 [details] gzip of /var/tmp/portage/www-client/firefox-10.0.5/temp/build.log
Created attachment 319332 [details] output of `emerge --info '=www-client/firefox-10.0.5'`
Also, as requested by the build.log: # emerge -pqv '=www-client/firefox-10.0.5' [ebuild N ] www-client/firefox-10.0.5 USE="alsa crashreporter dbus ipc libnotify minimal startup-notification webm -bindist -custom-cflags -custom-optimization -debug -pgo (-selinux) -system-sqlite -wifi" LINGUAS="-af -ak -ar -as -ast -be -bg -bn_BD -bn_IN -br -bs -ca -cs -csb -cy -da -de -el -en_GB -en_ZA -eo -es_AR -es_CL -es_ES -es_MX -et -eu -fa -fi -fr -fy_NL -ga_IE -gd -gl -gu_IN -he -hi_IN -hr -hu -hy_AM -id -is -it -ja -kk -kn -ko -ku -lg -lt -lv -mai -mk -ml -mr -nb_NO -nl -nn_NO -nso -or -pa_IN -pl -pt_BR -pt_PT -rm -ro -ru -si -sk -sl -son -sq -sr -sv_SE -ta -ta_LK -te -th -tr -uk -vi -zh_CN -zh_TW -zu" When I ran that command before beginning the actual emerge, it showed 42 packages to be installed. The others seem to have succeeded.
does binutils 2.22 work ? we're in the process of stabilizing that.
If binutils 2.22 isn't stable yet, would it make more sense to try a pre-2.21 version? Firefox only requires >=2.16.1. In other words, do you think the problem is specific to binutils 2.21?
Created attachment 319428 [details] gzip of /var/tmp/portage/www-client/firefox-10.0.5/temp/build.log with binutils-2.20.1-r1 With sys-devel/binutils-2.20.1-r1 installed, firefox compilation still fails, but with different errors. Now I get multiple instances of fatal error: opening dependency file .deps/*.pp: Input/output error (where *.pp is a different file in each error message). New build.log attached. emerge --info is identical to what's already attached, other than the binutils version number. It seems unlikely that I'm the first person to try to emerge firefox-10.0.5 with one of these levels of binutils on the system, which implies to me that there is something else behind this bug other than an incompatible level of binutils.
