public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: stage4 bootstrap exits with error 2 on 32-bit Debian arm-linux-gnueabi
Date: Wed, 11 May 2022 19:20:31 +0100	[thread overview]
Message-ID: <CAH6eHdQZZhr2pQkrdbagzv6b_+ciOXdNq16k4OHtZjHGAc4f8A@mail.gmail.com> (raw)
In-Reply-To: <c448a877-700a-46ad-3d58-5b241fee4b99@blastwave.org>

On Wed, 11 May 2022 at 18:52, Dennis Clarke <dclarke@blastwave.org> wrote:
>
> On 5/11/22 12:21, Jonathan Wakely wrote:
> > On Wed, 11 May 2022 at 16:16, Dennis Clarke via Gcc-help
> > <gcc-help@gcc.gnu.org> wrote:
> >> If anyone wonders why the bootstrap4 then the only answer I have is "why
> >> not?" given what I see at : https://gcc.gnu.org/install/build.html
> >
> > Is "because it doesn't work" a good enough answer?
>
> Ha.  Well I would not know that unless I tried.
> The results sure look pretty :
>
> io#
> io# ls -ltr --full-time */xgcc
> -rwxr-xr-x 1 dclarke devl 5743712 2022-05-10 17:20:58.783980821 +0000
> stage1-gcc/xgcc
> -rwxr-xr-x 1 dclarke devl 2514244 2022-05-10 22:54:53.878374286 +0000
> stage2-gcc/xgcc
> -rwxr-xr-x 1 dclarke devl 6378164 2022-05-11 02:04:07.126706718 +0000
> prev-gcc/xgcc
> -rwxr-xr-x 1 dclarke devl 6378164 2022-05-11 05:21:43.023573431 +0000
> gcc/xgcc
> io#
> io#
> io# openssl dgst -blake2s256 -r prev-gcc/xgcc gcc/xgcc
> 9cd9210dc9b0db574ea005e1cd83cc2013d071060fdb4f239aa09060e5b3db5f
> *prev-gcc/xgcc
> 9cd9210dc9b0db574ea005e1cd83cc2013d071060fdb4f239aa09060e5b3db5f *gcc/xgcc
> io#
>
> The result from stage3 perfectly matches stage4 and that is a good thing.
>
> >
> > Can you just try "make -j2" instead, without bootstrap4?
>
> Yep. No idea why a bootstrap fails but sure, I can just do the make and
> see what happens.

"make" and "make bootstrap" are the same. What I'm suggesting is you
don't use "make bootstrap4".

I didn't even know bootstrap4 existed, and I doubt anybody tests it.

Keep it simple. Don't do fancy things you don't need.

      reply	other threads:[~2022-05-11 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 15:13 Dennis Clarke
2022-05-11 16:21 ` Jonathan Wakely
2022-05-11 17:52   ` Dennis Clarke
2022-05-11 18:20     ` Jonathan Wakely [this message]

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=CAH6eHdQZZhr2pQkrdbagzv6b_+ciOXdNq16k4OHtZjHGAc4f8A@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=dclarke@blastwave.org \
    --cc=gcc-help@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).