From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Jean-Pierre Cartal <jean-pierre@cartal.fr>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] Make 4.3 and printvars
Date: Fri, 3 Jun 2022 16:43:19 +0200 [thread overview]
Message-ID: <20220603164319.26afc2a6@windsurf> (raw)
In-Reply-To: <6478648f-ffb3-cda2-66ad-3758ead25319@mind.be>
Hello,
On Fri, 3 Jun 2022 16:05:18 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> I tested it myself and indeed, it works!
>
> It would be great if someone could hack this into the Makefile itself (so that
> it recurses if ulimit -s is not high enough) and revert 25cec5ea733251.
FYI, the make 4.3 bug is resolved upstream:
https://git.savannah.gnu.org/cgit/make.git/commit/?id=e49e11e069fe7f214263be1782242b9b50f71eaa
I have asked upstream to issue a new release:
https://savannah.gnu.org/bugs/?59093
but not feedback so far.
So this workaround of "ulimit -s <highvalue>" should only be needed for
make 4.3. Later versions are supposed to be fixed.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-03 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e123582d-c613-f81a-ac0d-b23bc4d3e74a@cartal.fr>
2022-06-03 14:05 ` [Buildroot] Make 4.3 and printvars Arnout Vandecappelle
2022-06-03 14:25 ` Giulio Benetti
2022-06-03 14:29 ` Giulio Benetti
2022-06-03 14:43 ` Thomas Petazzoni via buildroot [this message]
2022-06-04 8:19 ` Yann E. MORIN
2022-06-04 18:50 ` Giulio Benetti
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=20220603164319.26afc2a6@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=jean-pierre@cartal.fr \
--cc=thomas.petazzoni@bootlin.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