All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: Daniel Price <daniel.price@gmail.com>,
	Martin Bark <martin@barkynet.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] Config.in: Introduce BR2_HOST_GCC_AT_LEAST_11
Date: Fri, 3 Nov 2023 21:16:07 +0100	[thread overview]
Message-ID: <20231103211607.04892bc0@windsurf> (raw)
In-Reply-To: <20231103000650.195673-1-adam.duskett@amarulasolutions.com>

On Thu,  2 Nov 2023 18:06:49 -0600
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:

> NodeJS 20 requires gcc >= 10.1. Unfortuantly, the only host gcc that has a
> decimal place is 4.9, and every other HOST_GCC_AT_LEAST is an even release,
> we round up to 11.
> 
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
>  Config.in | 10 ++++++++++
>  Makefile  |  2 +-
>  2 files changed, 11 insertions(+), 1 deletion(-)

Applied to master with an improved commit title and commit log. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-11-03 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  0:06 [Buildroot] [PATCH] Config.in: Introduce BR2_HOST_GCC_AT_LEAST_11 Adam Duskett
2023-11-03  0:06 ` [Buildroot] [PATCH] package/nodejs: bump version to 20.9.0 Adam Duskett
2023-11-03 20:16   ` Thomas Petazzoni via buildroot
2023-11-11 16:31     ` Romain Naour
2023-11-04 16:26   ` Arnout Vandecappelle via buildroot
2023-11-07 17:02     ` Yann E. MORIN
2023-11-03 20:16 ` Thomas Petazzoni via buildroot [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=20231103211607.04892bc0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=daniel.price@gmail.com \
    --cc=martin@barkynet.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.