Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Jens Maus <mail@jens-maus.de>
Cc: Daniel Price <daniel.price@gmail.com>,
	Martin Bark <martin@barkynet.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/nodejs: fix parallel build
Date: Sun, 24 Sep 2023 11:56:19 +0200	[thread overview]
Message-ID: <20230924095619.GG1469982@scaer> (raw)
In-Reply-To: <20230923160411.3662885-1-mail@jens-maus.de>

Jens, All,

On 2023-09-23 18:04 +0200, Jens Maus via buildroot spake thusly:
> In ninja-based nodejs builds performing parallel builds using "make -jX"
> is not working during buildroot initiated builds because the JOBS
> variable is not set in the MAKE_OPTS variables in nodejs.mk. This commit
> remedies the issue by setting JOBS to BR2_JLEVEL.

I was very confused that nodejs would not build in parallel; that would
have made for very, very,very long builds. And indeed, it does build in
parallel, in fact.

However, what it does, is use as many CPUs as are available, without
accounting for the value set by the user in BR2_JLEVEL, thus
overshooting the limits set by the user.

So, I reworded the whoe commit log to explain that.

Applied to master, thanks.

Regards,
Yann E. MORIN.

> Signed-off-by: Jens Maus <mail@jens-maus.de>
> 
> ---
> Changes v1 -> v2:
>   - removed unrelated v8-qemu-wrapper.in change (Yann)
>   - revised change summary (Yann)
>   - removed unnecessary top-level Makefile modifications (Yann)
> 
> Signed-off-by: Jens Maus <mail@jens-maus.de>
> ---
>  package/nodejs/nodejs.mk | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/package/nodejs/nodejs.mk b/package/nodejs/nodejs.mk
> index fe629ada21..4e70bd71a3 100644
> --- a/package/nodejs/nodejs.mk
> +++ b/package/nodejs/nodejs.mk
> @@ -46,14 +46,16 @@ HOST_NODEJS_MAKE_OPTS = \
>  	CXXFLAGS="$(HOST_NODEJS_CXXFLAGS)" \
>  	LDFLAGS.host="$(HOST_LDFLAGS)" \
>  	NO_LOAD=cctest.target.mk \
> -	PATH=$(@D)/bin:$(BR_PATH)
> +	PATH=$(@D)/bin:$(BR_PATH) \
> +	JOBS=$(BR2_JLEVEL)
>  
>  NODEJS_MAKE_OPTS = \
>  	$(TARGET_CONFIGURE_OPTS) \
>  	NO_LOAD=cctest.target.mk \
>  	PATH=$(@D)/bin:$(BR_PATH) \
>  	LDFLAGS="$(NODEJS_LDFLAGS)" \
> -	LD="$(TARGET_CXX)"
> +	LD="$(TARGET_CXX)" \
> +	JOBS=$(BR2_JLEVEL)
>  
>  # nodejs's build system uses python which can be a symlink to an unsupported
>  # python version (e.g. python 3.10 with nodejs 14.18.1). We work around this by
> -- 
> 2.34.1
> 
> _______________________________________________
> 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-09-24  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23  9:39 [Buildroot] [PATCH] package/nodejs: fix parallel build Jens Maus via buildroot
2023-09-23 10:09 ` Yann E. MORIN
2023-09-23 11:07   ` Jens Maus via buildroot
2023-09-23 16:20     ` Jens Maus via buildroot
2023-09-23 10:59 ` [Buildroot] [PATCH 1/1] package/nodejs: fix cross-compile builds Jens Maus via buildroot
2023-09-24 16:36   ` Yann E. MORIN
2023-09-27 11:46   ` Peter Korsgaard
2023-09-23 16:04 ` [Buildroot] [PATCH v2] package/nodejs: fix parallel build Jens Maus via buildroot
2023-09-24  9:56   ` Yann E. MORIN [this message]
2023-09-26  8:53     ` Peter Korsgaard

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=20230924095619.GG1469982@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=mail@jens-maus.de \
    --cc=martin@barkynet.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