Summary: | gcc-3.3: emerge gtk+-2.2.1-r1 fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | FL <flonai> |
Component: | [OLD] GCC Porting | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | foser, gnome, heijs, superman53142 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
FL
2003-05-19 15:48:16 UTC
seems to be too the hammer problem. i don't know but with the hammer patch there are *pixbuff issues. well i could recompile it with gcc-3.3 without the hammer patch applied *** Bug 21972 has been marked as a duplicate of this bug. *** I have the same error on my pentium4 I also tried to emerge it after I emerge gcc-3.3 without the hammer patch, but it still fails with the same error :-( http://forums.gentoo.org/viewtopic.php?p=358600#358600 I had exactly the same problem; recompling glib-1 and glib-2 with new CFLAGS, and then building GTK2 with new CFLAGS, did the trick for me. The compiler died when building GTK2 with -ftracer, but finally worked with the following: # gcc --version gcc (GCC) 3.3 (Gentoo Linux 1.4, PVR 3.3) # cat /var/db/pkg/x11-libs/gtk+-2.2.1_p1/CFLAGS -fprofile-arcs -march=pentium3 -finline-functions -fweb -frename-registers -fforce-addr -Os -pipe -g -g -g After I compiled glib with gcc-3.3 without the hammer patch, I could compile gtk+ correctly. I would say: remove the hammer patch at least for non athlon machines... I don't think this bug exists anymore :-) Resolving as fixed due to Comment #7. If this is not the case, then feel free to re-open the bug. |