Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Failed to emerge sys-devel/gcc-4.6.3
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
eurabilis
n00b
n00b


Joined: 22 Jun 2010
Posts: 66
Location: Warwick, Rhode island, USA

PostPosted: Fri Jan 11, 2013 12:57 am    Post subject: Failed to emerge sys-devel/gcc-4.6.3 Reply with quote

If one of you could help me understand how to fix this I would appreciate it. If you need any other information on my system just ask. Thanks.
I googled this but all the results talk about a bug but it was years ago so this must be something different.


Comparing stages 2 and 3
warning: gcc/cc1-checksum.o differs
warning: gcc/cc1plus-checksum.o differs
Bootstrap comparison failure!
gcc/varasm.o differs
make[2]: *** [compare] Error 1
make[2]: Leaving directory `/home/tmp/portage/sys-devel/gcc-4.6.3/work/build'
make[1]: *** [stage3-bubble] Error 2
make[1]: Leaving directory `/home/tmp/portage/sys-devel/gcc-4.6.3/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
* ERROR: sys-devel/gcc-4.6.3 failed (compile phase):
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4047: Called toolchain_src_compile
* environment, line 4707: Called gcc_do_make
* environment, line 2358: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`.
*
* Please include /home/tmp/portage/sys-devel/gcc-4.6.3/work/build/gcc-build-logs.tar.bz2 in your bug report
*
* The complete build log is located at '/home/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'.
* The ebuild environment file is located at '/home/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'.
* Working directory: '/home/tmp/portage/sys-devel/gcc-4.6.3/work/build'
* S: '/home/tmp/portage/sys-devel/gcc-4.6.3/work/build'

>>> Failed to emerge sys-devel/gcc-4.6.3, Log file:

>>> '/home/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'

* Messages for package dev-libs/ppl-0.11.2-r1:

* After an upgrade of PPL it is important that you rebuild
* dev-libs/cloog-ppl.
*
* If you use gcc-config to switch to an older compiler version than
* the one PPL was built with, PPL must be rebuilt with that version.
*
* In both cases failure to do this will get you this error when
* graphite flags are used:
*
* sorry, unimplemented: Graphite loop optimizations cannot be used
*

* Messages for package sys-libs/glibc-2.15-r3:

* Defaulting /etc/host.conf:multi to on
* Generating all locales; edit /etc/locale.gen to save time/space

* Messages for package sys-devel/gcc-4.6.3:

*
* LTO support is still experimental and unstable.
* Any bugs resulting from the use of LTO will not be fixed.
*
* ERROR: sys-devel/gcc-4.6.3 failed (compile phase):
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4047: Called toolchain_src_compile
* environment, line 4707: Called gcc_do_make
* environment, line 2358: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`.
*
* Please include /home/tmp/portage/sys-devel/gcc-4.6.3/work/build/gcc-build-logs.tar.bz2 in your bug report
*
* The complete build log is located at '/home/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'.
* The ebuild environment file is located at '/home/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'.
* Working directory: '/home/tmp/portage/sys-devel/gcc-4.6.3/work/build'
* S: '/home/tmp/portage/sys-devel/gcc-4.6.3/work/build'

* Regenerating GNU info directory index...
* Processed 109 info files.
gentoo mike #
_________________
--
I am my only local user and I cannot be trusted. This is a generally a very bad thing. Thing is, with *nix where there is a shell there is a way.
Back to top
View user's profile Send private message
fturco
Apprentice
Apprentice


Joined: 08 Dec 2010
Posts: 273
Location: Italy

PostPosted: Fri Jan 11, 2013 2:07 pm    Post subject: Reply with quote

Please post the output of:
Code:
emerge --info

This time using BBCode tags, if possible.
Back to top
View user's profile Send private message
kite14
Tux's lil' helper
Tux's lil' helper


Joined: 07 Nov 2006
Posts: 140
Location: Pordenone/Italy

PostPosted: Fri Jan 11, 2013 2:47 pm    Post subject: Reply with quote

Code:
...
Comparing stages 2 and 3
warning: gcc/cc1-checksum.o differs
warning: gcc/cc1plus-checksum.o differs
Bootstrap comparison failure!
...

You are not alone → https://bugs.gentoo.org/show_bug.cgi?id=411333
Discussion here on this thread → http://forums.gentoo.org/viewtopic-t-924620-highlight-.html
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum