Summary: | sys-devel/gcc-4.4.2 fails to build (on a slightly outdated installation) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rumi Szabolcs <rumi> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Full build log |
Description
Rumi Szabolcs
2010-02-02 04:03:51 UTC
Please, attach full build.log. Created attachment 218139 [details]
Full build log
i cant see any reason why that would fail. please run: cd /usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/build/gcc /usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/build/./prev-gcc/xgcc -B/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/build/./prev-gcc/ -B/usr/i686-pc-linux-gnu/bin/ -c -march=i686 -O2 -pipe -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Icp -I/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc -I/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc/cp -I/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc/../include -I/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc/../libcpp/include -I/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc/../libdecnumber -I/usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc/../libdecnumber/bid -I../libdecnumber /usr/src/gentoo/tmp/medion/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/gcc/cp/cp-lang.c -o cp/cp-lang.o if that still fails for the same reason, change the "-c" to "-E -dD", the "cp-lang.o" to "cp-lang.i", and post the resulting file as an attachment Well, I didn't see any reason for it to fail either but it did... This may be a rare situation as most people probably went to gcc-4.4 through gcc-4.3 and not straight from 4.1. I suspect that the problem may be related to this because those installations with whom I went through 4.3.x I haven't experienced this error. I'm terribly sorry but I cannot provide any more feedback as I had to make the affected machine usable so it's not in this particular state anymore. It's up to you whether you close this bug or wait for somebody else to confirm and help to diagnose it further. Can't reproduce this either. |