From: Alan Grimes <ALONZOTG@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gcc 5.3
Date: Thu, 24 Dec 2015 11:05:42 -0500 [thread overview]
Message-ID: <567C17D6.7090702@verizon.net> (raw)
In-Reply-To: <567C11CB.4080000@gmail.com>
It has been many moons since I got into compiling a compiler but here's
how it basically works:
STAGE 1:
Compile the new compiler with whatever broken crap compiler is already
installed/hacked together/manually entered by punch cards/etc...
STAGE 2:
Compile the new compiler with whatever came out of stage 1.
STAGE 3:
As a sanity check, compile the new compiler a third time with whatever
came out of stage 2
Because stage 1 should have produced a fully updated compiler, it's
output (stage 2) should be identical to what that compiler in turn
produced (Stage 3).
This is where it's failing for me.
Stanislav Nikolov wrote:
> I think they should be compiled with the same version of gcc,
> shouldn't they?
>
> On 12/24/2015 05:18 PM, Alan Grimes wrote:
> > Hey, thanks for putting out gcc 5.3...
>
> > Unfortunately, it fails to bootstrap on my machine. I am getting
> > differences between the stage 2 and stage 3 compilers and it's
> dying... =(
>
> > make[2]: Entering directory
> > '/var/tmp/portage/sys-devel/gcc-5.3.0/work/build'
> > make[3]: Entering directory
> > '/var/tmp/portage/sys-devel/gcc-5.3.0/work/build'
> > rm -f stage_current
> > make[3]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-5.3.0/work/build'
> > Comparing stages 2 and 3
> > warning: gcc/cc1plus-checksum.o differs
> > warning: gcc/cc1-checksum.o differs
> > Bootstrap comparison failure!
> > gcc/tree-ssa-threadedge.o differs
> > gcc/tsan.o differs
> > gcc/print-tree.o differs
> > gcc/df-core.o differs
> > gcc/omega.o differs
> > gcc/dwarf2cfi.o differs
> > gcc/lto-cgraph.o differs
> > gcc/sanopt.o differs
> > gcc/sched-vis.o differs
> > gcc/tree-ssa-tail-merge.o differs
> > gcc/godump.o differs
> > gcc/graph.o differs
> > gcc/tree-vect-loop-manip.o differs
> > gcc/cse.o differs
> > gcc/omp-low.o differs
>
> > [many lines omitted]
>
> > libiberty/xmalloc.o differs
> > libiberty/simple-object-elf.o differs
> > libiberty/spaces.o differs
> > libiberty/pex-unix.o differs
> > libiberty/simple-object-coff.o differs
> > libiberty/crc32.o differs
> > libiberty/physmem.o differs
> > libiberty/make-relative-prefix.o differs
> > libiberty/argv.o differs
> > libiberty/pex-common.o differs
> > libiberty/simple-object.o differs
> > libiberty/strerror.o differs
> > libiberty/simple-object-mach-o.o differs
> > libiberty/sha1.o differs
> > libiberty/cp-demint.o differs
> > libiberty/dyn-string.o differs
> > libiberty/make-temp-file.o differs
> > libiberty/cplus-dem.o differs
> > libiberty/sort.o differs
> > libiberty/splay-tree.o differs
> > libiberty/xstrndup.o differs
> > lto-plugin/.libs/lto-plugin.o differs
> > Makefile:19638: recipe for target 'compare' failed
> > make[2]: *** [compare] Error 1
> > make[2]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-5.3.0/work/build'
> > Makefile:19617: recipe for target 'stage3-bubble' failed
> > make[1]: *** [stage3-bubble] Error 2
> > make[1]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-5.3.0/work/build'
> > Makefile:19691: recipe for target 'bootstrap-lean' failed
> > make: *** [bootstrap-lean] Error 2
> > * ERROR: sys-devel/gcc-5.3.0::gentoo failed (compile phase):
> > * emake failed
>
>
>
> >
--
IQ is a measure of how stupid you feel.
Powers are not rights.
next prev parent reply other threads:[~2015-12-24 16:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 15:18 [gentoo-user] Gcc 5.3 Alan Grimes
2015-12-24 15:39 ` Stanislav Nikolov
2015-12-24 16:05 ` Alan Grimes [this message]
2015-12-24 20:17 ` David Haller
2015-12-25 16:01 ` Alan Grimes
2015-12-24 22:05 ` Paul Colquhoun
2015-12-25 12:47 ` Andreas K. Huettel
2015-12-25 15:42 ` Alan Grimes
2015-12-25 20:40 ` [gentoo-user] " walt
2015-12-26 3:00 ` Paul Colquhoun
2015-12-26 5:44 ` Paul Colquhoun
2016-01-01 15:51 ` Stefan G. Weichinger
2015-12-26 6:25 ` David Haller
2015-12-26 8:40 ` Philip Webb
2015-12-28 8:17 ` Andrew Savchenko
2015-12-29 12:52 ` lee
2015-12-29 14:54 ` David Haller
2015-12-29 18:21 ` lee
2015-12-29 22:48 ` Neil Bothwick
2015-12-30 16:32 ` lee
2015-12-30 22:33 ` Paul Colquhoun
2016-01-01 10:37 ` lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=567C17D6.7090702@verizon.net \
--to=alonzotg@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox