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] package/nodejs: bump version to 20.9.0
Date: Fri, 3 Nov 2023 21:16:11 +0100 [thread overview]
Message-ID: <20231103211611.0dc93419@windsurf> (raw)
In-Reply-To: <20231103000650.195673-2-adam.duskett@amarulasolutions.com>
On Thu, 2 Nov 2023 18:06:50 -0600
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> - Refactor 0001-add-qemu-wrapper-support.patch for 20.9.0
>
> - NodeJS now requires GCC 10.1 header. However, as there is no
> BR2_TOOLCHAIN_GCC_AT_LEAST_10_1, we round up to BR2_TOOLCHAIN_GCC_AT_LEAST_11.
>
> - Drop the --without-dtrace and --without-etw config options as they no longer
> exist.
>
> - Update support/testing/tests/package/test_nodejs.py to use
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN, otherwise the test fails as the
> gcc version selected will be 7.
>
> - Update the hash file for LICENSE.txt due to numerous changes, such
> as the addition of new libraries and updated dates. No new license
> types are added.
>
> Tested with: ./support/testing/run-tests tests.package.test_nodejs
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
> package/nodejs/Config.in | 8 +--
> .../0001-add-qemu-wrapper-support.patch | 51 ++++++++++++-------
> ...ules-cjs-loader.js-adjust-default-pa.patch | 2 +-
> package/nodejs/nodejs-src/nodejs-src.mk | 4 --
> package/nodejs/nodejs.hash | 15 +++---
> package/nodejs/nodejs.mk | 2 +-
> support/testing/tests/package/test_nodejs.py | 3 ++
> 7 files changed, 50 insertions(+), 35 deletions(-)
Applied to master, 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
next prev 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 [this message]
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 ` [Buildroot] [PATCH] Config.in: Introduce BR2_HOST_GCC_AT_LEAST_11 Thomas Petazzoni via buildroot
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=20231103211611.0dc93419@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox