Summary: | gcc-3.3.3-r6 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Ruskin <aoyu93> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | merlin |
Priority: | High | ||
Version: | 2004.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Ruskin
2004-06-09 15:59:21 UTC
That is pretty odd.. could you rm -rf /var/tmp/portage/* and try to make it fail again? quote: could you rm -rf /var/tmp/portage/* and try to make it fail again? I did that and failure is identical. tseng there sorta seems to be a common thread here. It's 2.6.x users (probably headers?) that are reporting problems with the toolchain. I got it to build after building development-sources-2.6.7_rc3. The kernel options when gcc failed were: - no pre-emption - packet-writing patch http://w1.894.telia.com/~u89404340/patches/packet/2.6/packet-2.6.6.patch.bz2 With preemption selected and no packet-writing patch, the kernel enabled gcc to build. I don't know which is the culprit but I suspect the packet-writing. I had this exact error message when trying to update gcc while running 2.6.5-gentoo-r1/i686. After trying literally everything, I upgraded the kernel to 2.6.7-gentoo-r5/i686 and gcc compiled perfectly fine. More info available here: http://forums.gentoo.org/viewtopic.php?p=1275413#1275413 gcc-3.3.4-rX is the current stable. Please emerge rsync and test with that. gcc-3.3.4-r1 builds OK here, but I'm not currently using the packet-writing patch. |