From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Martin Bark <martin@barkynet.com>,
Daniel Price <daniel.price@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nodejs/nodejs-src: remove .node files with different architecture
Date: Tue, 7 Nov 2023 21:40:23 +0100 [thread overview]
Message-ID: <20231107204023.GG229059@scaer> (raw)
In-Reply-To: <829232c3-9456-4bf8-91dd-506cb7554649@mind.be>
Arnout, All,
On 2023-11-07 21:08 +0100, Arnout Vandecappelle spake thusly:
> On 07/11/2023 17:15, Yann E. MORIN wrote:
> >On 2023-11-05 15:27 +0100, Giulio Benetti spake thusly:
> >>On 03/11/23 22:21, Yann E. MORIN wrote:
> >>>Oh, I was just walking the "npm is a mess anyway, just ignore anything
> >>>from it, we don't care" road. If we take this stance, then
> >>>_BIN_ARCH_EXCLUDE is a trivial way to avoid the check-bin-arch issue.
> >[--SNIP--]
> >>Since npm rebuilding is not that easy and fast to deal with I've just sent
> >>this patch to temporary exclude the /usr/lib/node_modules folder
> >>as you've suggested(forgotten to add "Suggested-by: Yann E. MORIN
> >><yann.morin.1998@free.fr>").
> >>
> >>Later I hope to find time to deal with npm rebuilding.
> >
> >I think tht it might in fact be what we're doing already, as we use:
> > npm_config_build_from_source=true
> >
> >in the environment when we call npm.
>
> I guess that even if the binaries for the actual target get rebuilt, the
> other irrelevant binaries that were also downloaded are still there and
> trigger the issue.
Yes, absolutely, and confirmed by experience. ;-)
I'm still working on that patch...
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
prev parent reply other threads:[~2023-11-07 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 12:07 [Buildroot] [PATCH] package/nodejs/nodejs-src: remove .node files with different architecture Giulio Benetti
2023-11-01 15:21 ` Yann E. MORIN
2023-11-02 23:16 ` Giulio Benetti
2023-11-02 23:43 ` Giulio Benetti
2023-11-03 21:21 ` Yann E. MORIN
2023-11-05 14:27 ` Giulio Benetti
2023-11-07 16:15 ` Yann E. MORIN
2023-11-07 20:08 ` Arnout Vandecappelle via buildroot
2023-11-07 20:40 ` 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=20231107204023.GG229059@scaer \
--to=yann.morin.1998@free.fr \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=daniel.price@gmail.com \
--cc=giulio.benetti@benettiengineering.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.