As per summary, check attached build log.
And _please_ try not to fix it in the wrong way: http://blog.flameeyes.eu/2009/07/02/how-_not_-to-fix-gcc-4-4-bugs
Created attachment 198305 [details]
Created attachment 198454 [details]
Failed build log for Encode-Detect-1.01 on ~amd64 and GCC 4.3.3
On x86_64 Encode-Detect also fails during compilation.
I am using GCC 4.3.3 and fresh ~amd64 installation.
I can replicate this bug also on another installation ~x86 also with GCC 4.3.3
(In reply to comment #1)
> Created an attachment (id=198305) 
> Build log
Please change summary from "dev-perl/Encode-Detect: fails to build with gcc-4.4" to "dev-perl/Encode-Detect: fails to build both on x86 and x86_64" as this bug is not related to GCC and seems to be architecture wide/global bug.
Can you show your emerge --info? It really shouldn't hit that way on GCC 4.3…
It fails with gcc 4.3.2-r3 and ExtUtils-ParseXS-2.20 and works with 2.19.
It does not fail with gcc 4.4.0-r1 and perl-5.10.0 and ExtUtils-ParseXS-2.20 or 2.19
I'm getting the same errors as reported in the attached Encode-Detect-1.01:20090717-052252.log. I'm using gcc 4.3.3-r2, dev-perl/Encode-Detect-1.01, ~amd64, and perl-core/ExtUtils-ParseXS-2.20
+*ExtUtils-ParseXS-2.20-r1 (25 Jul 2009)
+ 25 Jul 2009; Mark Loeser <firstname.lastname@example.org>
+ -ExtUtils-ParseXS-2.20.ebuild, +ExtUtils-ParseXS-2.20-r1.ebuild,
+ Revbump to fix header for gcc-4.4 issue; bug #278155