Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] Makefile: disable 'printvars' and 'show-vars' recipes for Make 4.3
Date: Sat, 30 Jul 2022 14:22:16 +0200	[thread overview]
Message-ID: <20220730122216.GT3168@scaer> (raw)
In-Reply-To: <b48adde2-4418-178c-0148-ef7d46cdfe4a@mind.be>

Arnout, Giulio, James, All,

On 2022-07-27 10:38 +0200, Arnout Vandecappelle spake thusly:
> On 26/07/2022 23:52, Giulio Benetti wrote:
> >On 21/07/22 05:55, James Hilliard wrote:
> >>On Sat, Jan 1, 2022 at 2:40 PM Giulio Benetti
> >><giulio.benetti@benettiengineering.com> wrote:
> >>>Make 4.3 is buggy and leads to a "Segmentation fault (core dumped)" when
> >>>calling 'make printvars' or 'make show-vars', so let's refuse to execute
> >>>those recipes if Make 4.3 by adding 'check-make-version' recipe as
> >>>depedendency of 'printvars' and 'show-vars' as suggested by Yann E. Morin.
> >>FYI autobuilder threads seem to die when this gets hit:
[--SNIP--]
> >Do you have an autobuilder failure link?
> >So I can reproduce it here and find a work-around for it.
>  It's the autobuilder script (from the buildroot-test repository) itself
> that crashes. I suspect it isn't able to send in its results after that.
> There is a separate process for each autobuilder instance, but I don't think
> they are restarted when they crash so eventually all instances will die.
> 
>  Note that this is only invoked if a reproducibility error was detected.
> 
>  @James: do like Thomas, install an earlier make on your system :-)

That will no longer ne necessary, as we now have a working workaround
for that, that I just pushed:

    5c54c3ef3db2 Makefile: workaround make 4.3 issue for 'printvars and 'show-vars'

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-07-30 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 21:40 [Buildroot] [PATCH] Makefile: disable 'printvars' and 'show-vars' recipes for Make 4.3 Giulio Benetti
2022-01-04 17:15 ` Arnout Vandecappelle
2022-07-21  3:55 ` James Hilliard
2022-07-26 21:52   ` Giulio Benetti
2022-07-27  8:38     ` Arnout Vandecappelle
2022-07-30 12:22       ` Yann E. MORIN [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=20220730122216.GT3168@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=james.hilliard1@gmail.com \
    /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