From: Bastian Germann <bage@linutronix.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] kbuild: deb-pkg: Allow parallel build
Date: Mon, 13 Mar 2023 19:56:51 +0100 [thread overview]
Message-ID: <63232be8-59f6-8b93-96be-730f5126f60c@linutronix.de> (raw)
In-Reply-To: <CAK7LNARd8rQdwauAvgSo-+wxv=rU-4tTCtrzRJ2uhgWRrt6Xxw@mail.gmail.com>
Am 13.03.23 um 18:59 schrieb Masahiro Yamada:
> On Tue, Mar 14, 2023 at 2:10 AM Bastian Germann <bage@linutronix.de> wrote:
>>
>> Currently, the only way to build the deb-pkg generated package parallely
>> is adding -jN to the MAKEFLAGS environment variable. The package ignores
>> the usual parallel build option that is described in Debian Policy §4.9.1.
>
>
>
> "dpkg-buildpackage -b -j16" worked for me.
This ends up in DEB_BUILD_OPTIONS=parallel=16 being set and the call:
/usr/bin/make -f ./Makefile ARCH=x86 KERNELRELEASE=6.3.0-rc2 KBUILD_BUILD_VERSION=1 olddefconfig all
So it is not used to run the actual build, just the top level `make -f debian/rules` invocation.
You can set --jobs-force=16, which ends up in MAKEFLAGS but the point of the patch is that one can use
the usual way of parallelizing.
Side note: Without the patch, the build is run with -j1 regardless of being called from the Linux Makefile
or dpkg-buildpackage.
next prev parent reply other threads:[~2023-03-13 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 17:10 [PATCH 0/1] " Bastian Germann
2023-03-13 17:10 ` [PATCH 1/1] " Bastian Germann
2023-03-13 17:59 ` Masahiro Yamada
2023-03-13 18:56 ` Bastian Germann [this message]
2023-03-15 14:18 ` Masahiro Yamada
2023-03-15 15:51 ` Bastian Germann
2023-03-15 16:36 ` Masahiro Yamada
2023-03-15 15:56 ` Sedat Dilek
2023-03-15 16:39 ` Masahiro Yamada
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=63232be8-59f6-8b93-96be-730f5126f60c@linutronix.de \
--to=bage@linutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®