Summary: | sys-devel/gcc-4.4.3: fails to emerge with USE=graphite & gives errors with USE=gtk | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tbrass <brasfild> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | tomka |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/var/tmp/portage/sys-devel/gcc-4.4.3/temp/environment
/var/tmp/portage/sys-devel/gcc-4.4.3/temp/build.log |
Description
tbrass
2010-05-15 22:12:18 UTC
Created attachment 231601 [details]
/var/tmp/portage/sys-devel/gcc-4.4.3/temp/environment
Created attachment 231603 [details]
/var/tmp/portage/sys-devel/gcc-4.4.3/temp/build.log
Update -- another fresh install allowed me to emerge sys-devel/gcc-4.4.3 Installed versions: 4.4.3(4.4)!s(15:38:25 05/18/10)(default fortran graphite mudflap multilib multislot nls nptl objc objc++ objc-gc openmp -altivec -bootstrap -build -doc -fixed-point -gcj -gtk -hardened -libffi -n32 -n64 -nocxx -profiled -test -vanilla) BUT, I still encountered more than 20 errors in libgcc like this one: /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/libgcc/../gcc/unwind-dw2-fde.c:843: warning: dereferencing type-punned pointer will break strict-aliasing rules And: /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/libobjc/objects.c:49: warning: implicit declaration of function ‘GC_malloc_explicitly_typed’ /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/libobjc/objects.c:49: warning: implicit declaration of function ‘GC_malloc_explicitly_typed’ Key differences? I changed my LDFLAGS="-Wl,-O1" and MAKEOPTS=1 (in addition to jobs=1) and USE=-gtk The strict-aliasing and other warnings aren't errors, they're warnings. You shouldn't need to worry about them. Also, the gtk USE flag on gcc only has an effect when the gcj flag is also enabled, so it shouldn't make any differences. The actual error you're getting is: In file included from /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree-ssa-pre.c:29: /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:1374: error: expected declaration specifiers or '...' before '(' token /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:1375: error: return type is an incomplete type [...] In file included from /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree-ssa-pre.c:29: /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:3423: error: field 'int_cst' has incomplete type /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:3424: error: field 'real_cst' has incomplete type /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:3425: error: field 'fixed_cst' has incomplete type /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:3426: error: field 'vector' has incomplete type /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:3427: error: field 'string' has incomplete type /var/tmp/portage/sys-devel/gcc-4.4.3/work/gcc-4.4.3/gcc/tree.h:3428: error: field 'complex' has incomplete type make[3]: *** [tree-ssa-pre.o] Error 1 That said, there is no version named "gcc-4.4.3" currently in the tree. I'm not sure where you're getting it from. The version currently in the tree is "gcc-4.4.3-r2". Can you run emerge --sync and try again with that version? (emerge -av gcc:4.4 should do it) Hi Ryan, I followed your suggestions & successfully rebuilt GCC. I still can't get it to build with USE=gtk gcj, but that isn't crucial for me. One thing that may have helped, I mounted a tmpfs /var/tmp/portage build location. Perhaps BTRFS or my HD could have contributed to the errors that you pointed out? Thanks again for your help. -TB |