Buildroot Archive mirror
 help / color / mirror / Atom feed
From: Sam Wang <pt.skyin@gmail.com>
To: buildroot@buildroot.org
Subject: [Buildroot] Fwd: BR2_MAKE makes "Rebuilding kernel with initramfs" use -j1
Date: Sat, 18 May 2024 18:31:58 +0800	[thread overview]
Message-ID: <CAEu2X4H2cMERvvwd2dR-3v1VaM+WXgxVgpMVtuP4Zi1uhZ4iDw@mail.gmail.com> (raw)
In-Reply-To: <CAEu2X4E5UCYXo7D1tB6P=rTTOZywQ43Pm7dg1d0=xpn6TAtbJg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]

Dear buildroot developer,

I'm using buildroot 2024.02.1 with top-level parallel build, and found in
the last step of my build - "Rebuilding kernel with initramfs" - it throws
the following warning and makes the kernel rebuilding single threaded.

*make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent
make rule.*

The previous version 2023.02.4 didn't have this issue. And, I found this
commit: linux: use BR2_MAKE · buildroot/buildroot@0b9efc9 · GitHub
<https://github.com/buildroot/buildroot/commit/0b9efc991f8a2c1b6388e4e575641228262eadd1>,
which changes $(MAKE) to $(BR2_MAKE)". I reverted the change in line 645
back to $(MAKE) in my repo, and the warning was gone, and the kernel
rebuild was in multi-thread again.

Wondering if I missed something in the buildroot configuration or this part
of BR2 code needs some revision? Thanks for your help!

Best regards,
Sam

[-- Attachment #1.2: Type: text/html, Size: 1392 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

           reply	other threads:[~2024-05-18 10:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAEu2X4E5UCYXo7D1tB6P=rTTOZywQ43Pm7dg1d0=xpn6TAtbJg@mail.gmail.com>]

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=CAEu2X4H2cMERvvwd2dR-3v1VaM+WXgxVgpMVtuP4Zi1uhZ4iDw@mail.gmail.com \
    --to=pt.skyin@gmail.com \
    --cc=buildroot@buildroot.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).