public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44959] [4.5 Regression] bootstrap failed at Comparing stages 2 and 3
Date: Tue, 08 May 2012 20:50:00 -0000	[thread overview]
Message-ID: <bug-44959-4-TwpIssO99k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44959-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44959

--- Comment #23 from Hin-Tak Leung <htl10 at users dot sourceforge.net> 2012-05-08 20:48:25 UTC ---
(In reply to comment #22)
> > --- Comment #21 from Hin-Tak Leung <htl10 at users dot sourceforge.net> 2012-05-08 14:15:52 UTC ---
> 
> I think there was a misunderstanding: I specificially asked for the
> smallest of the differing .o files *other than cc1*-checksum.o* since
> the latter are expected to differ between stages.  But for the moment, I
> think we can do with cc1-checksum.o alone.

Okay, sorry about that.

> > There are two curious things:
> > 1. why does the 2nd stage drops to only about 600 byte. (I assume 20-30k is
> > normal).
> 
> That's certainly completely unexpected.  I'd ask you to rebuild
> cc1-checksum.o for stage2 and stage3 (move the .o's aside, run make -n
> cc1-checksum.o, then manually add -v -save-temps to the compilation
> line.  Then attach a tarball with the .c and output files and the gcc -v
> output to see if there are any obvious diffences between the compilations.

I'll get round to it when I find some time to do so, soon.

> > 2. I did have a success with 4.6.1 (and I believe with both make/make
> > bootstrap4 or 4-lean) a while ago, therefore I closed the bug. I did not
> 
> Please always try this with a plain make/make bootstrap.  I don't
> currently want to debug issues which might be caused by non-default
> targets.  I don't see why they should be, but please let us stay with
> the basics.

Out of the three attachments, one is with plain make, the other two, one with
bootstrap4 and bootstrap4-lean. (I think I tried them in the order of 4-lean,
4, plain - so you could see which is which from the time stamp). I know what
you are saying, that's why I tried it simplier and simpler :-(.

> > install 4.6.1 at the time but stayed at 4.3.3 (mostly to test and verify the
> > other issues), but now I cannot build 4.6.1 correctly again. The system has not
> > been changed much since then, the only changes I can think of which is relevant
> > is that I installed updated versions of the gcc dependencies
> > (mpfr-3.1.0,mpc-0.9,gmp-5.0.5)
> > from the most updated versions the last time I looked at gcc.
> 
> This is certainly a problem: the installation guide states
> 
>    Several support libraries are necessary to build GCC, some are required,
>    others optional. While any sufficiently new version of required tools
>    usually work, library requirements are generally stricter. Newer
>    versions may work in some cases, but it's safer to use the exact
>    versions documented. We appreciate bug reports about problems with newer
>    versions, though.
> 
> The sentence about newer versions is there for a reason.  In fact, on
> Tru64 UNIX the situation is even worse: gmp 4.3.2 make check fails for
> me, so I'm currently staying with gmp 4.2.1, mpfr 2.3.2, and mpc 0.8.
> 
> Before using *any* version of gmp/mpfr/mpc with gcc (or for any other
> purpose), make sure that they pass make check, as prominently stated in
> e.g. the gmp announcements.
> 
>     Rainer

Argh :-(. I did run make check on one of them (gmp?) because it says so at the
end of make or 'make install', and it finished okay.

I can certainly go back - if it is worthwhile. I'll try to re-do the checksum
object files first.


  parent reply	other threads:[~2012-05-08 20:48 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44959-4@http.gcc.gnu.org/bugzilla/>
2010-11-14 12:01 ` rguenth at gcc dot gnu.org
2010-12-15  1:53 ` htl10 at users dot sourceforge.net
2010-12-16 13:28 ` rguenth at gcc dot gnu.org
2010-12-17 12:22 ` htl10 at users dot sourceforge.net
2011-04-28 15:40 ` rguenth at gcc dot gnu.org
2011-04-30  7:17 ` htl10 at users dot sourceforge.net
2011-04-30 11:00 ` htl10 at users dot sourceforge.net
2011-07-19 12:27 ` ro at gcc dot gnu.org
2011-08-02 11:08 ` htl10 at users dot sourceforge.net
2011-08-02 11:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-08-03 15:30 ` htl10 at users dot sourceforge.net
2011-08-03 15:33 ` htl10 at users dot sourceforge.net
2011-08-05  5:39 ` htl10 at users dot sourceforge.net
2012-05-07  7:09 ` htl10 at users dot sourceforge.net
2012-05-07 10:28 ` htl10 at users dot sourceforge.net
2012-05-07 12:42 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-05-08 14:08 ` htl10 at users dot sourceforge.net
2012-05-08 14:09 ` htl10 at users dot sourceforge.net
2012-05-08 14:16 ` htl10 at users dot sourceforge.net
2012-05-08 14:28 ` htl10 at users dot sourceforge.net
2012-05-08 15:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-05-08 20:50 ` htl10 at users dot sourceforge.net [this message]
2012-07-02  9:44 ` [Bug bootstrap/44959] [4.6 " rguenth at gcc dot gnu.org
2012-08-30 14:05 ` htl10 at users dot sourceforge.net
2012-08-30 14:19 ` htl10 at users dot sourceforge.net
2012-08-30 14:57 ` htl10 at users dot sourceforge.net
2012-08-30 17:32 ` htl10 at users dot sourceforge.net
2012-09-01  2:53 ` htl10 at users dot sourceforge.net
2012-09-01  8:18 ` htl10 at users dot sourceforge.net
2012-09-01  8:26 ` pinskia at gcc dot gnu.org
2012-09-01 11:23 ` htl10 at users dot sourceforge.net
2012-09-14 13:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-09-14 13:44 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-09-14 13:49 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-09-14 13:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-09-14 13:54 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-09-14 14:43 ` htl10 at users dot sourceforge.net
2013-04-12 16:13 ` jakub at gcc dot gnu.org
2013-04-15 12:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-11-10  8:11 ` pinskia at gcc dot gnu.org
2013-12-30  4:26 ` htl10 at users dot sourceforge.net
2013-12-30  4:58 ` htl10 at users dot sourceforge.net
2014-01-03 11:10 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-07-15 21:49 [Bug bootstrap/44959] New: [4.5 " htl10 at users dot sourceforge dot net
2010-07-16  8:30 ` [Bug bootstrap/44959] " rguenth at gcc dot gnu dot org
2010-07-22  8:55 ` rguenth at gcc dot gnu dot org
2010-07-31  9:35 ` rguenth at gcc dot gnu dot org

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=bug-44959-4-TwpIssO99k@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).