All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Daniel Price <daniel.price@gmail.com>,
	Martin Bark <martin@barkynet.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nodejs: fix additional modules installation
Date: Tue, 7 Nov 2023 22:51:57 +0100	[thread overview]
Message-ID: <20231107215157.GN229059@scaer> (raw)
In-Reply-To: <a9454b05-faf1-4b77-9247-79f028735fe1@othermo.de>

Marcus, All,

On 2023-11-06 20:12 +0100, Marcus Hoffmann via buildroot spake thusly:
> Thanks Guilio, this fixes our build problem!
> 
> On 31.10.23 10:01, Giulio Benetti wrote:
> >At the moment the npm_config_nodedir is set to the build directory but
> >npm nodedir must be the one on target to find the expected files. So let's
> >set npm_config_nodedir to $(TARGET_DIR)/usr.
> >
> >Fixes:
> >https://bugs.busybox.net/show_bug.cgi?id=15826
> >
> >Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> Tested-by: Marcus Hoffmann <marcus.hoffmann@othermo.de>

Thanks for providing your tested-by tag.

However, since I changed the patch to use STAGING_DIR instead of
TARGET_DIR, I dropped your tested-by, because the new code is now too
different from what you tested.

Still, seeing a Tested-by tag on such a patch gave me enough interest
to look deeper and investigate to find the actual issue and come up with
a better fix. So, thank you!

Regards,
Yann E. MORIN.

> >---
> >  package/nodejs/nodejs.mk | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/package/nodejs/nodejs.mk b/package/nodejs/nodejs.mk
> >index 2a8c570932..8f86413049 100644
> >--- a/package/nodejs/nodejs.mk
> >+++ b/package/nodejs/nodejs.mk
> >@@ -20,7 +20,7 @@ NODEJS_BIN_ENV = $(TARGET_CONFIGURE_OPTS) \
> >      npm_config_arch=$(NODEJS_CPU) \
> >      npm_config_target_arch=$(NODEJS_CPU) \
> >      npm_config_build_from_source=true \
> >-     npm_config_nodedir=$(BUILD_DIR)/nodejs-$(NODEJS_VERSION) \
> >+     npm_config_nodedir=$(TARGET_DIR)/usr \
> >      npm_config_prefix=$(TARGET_DIR)/usr \
> >      npm_config_cache=$(BUILD_DIR)/.npm-cache
> >
> ________________________________
> 
> othermo GmbH | Sitz der Gesellschaft: Alzenau | Amtsgericht Aschaffenburg: HRB 14783 | USt-IdNr.: DE319977978 | Geschäftsführung: Dr. Dennis Metz.
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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:[~2023-11-07 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  9:01 [Buildroot] [PATCH] package/nodejs: fix additional modules installation Giulio Benetti
2023-11-06 19:12 ` Marcus Hoffmann via buildroot
2023-11-07 21:51   ` Yann E. MORIN [this message]
2023-11-07 15:15 ` Yann E. MORIN
2023-11-07 17:27   ` Yann E. MORIN
2023-11-07 21:40 ` Yann E. MORIN

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=20231107215157.GN229059@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=marcus.hoffmann@othermo.de \
    --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.