From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Ben Hutchings <benh@debian.org>,
Ron Economos <re@w6rz.net>, Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH 2/3] kbuild: deb-pkg: add pkg.linux-upstream.nokernelheaders build profile
Date: Wed, 23 Oct 2024 17:38:08 +0200 [thread overview]
Message-ID: <ZxkYYLbiXZ3p59iu@fjasle.eu> (raw)
In-Reply-To: <20241022181703.1710116-2-masahiroy@kernel.org>
On Wed, Oct 23, 2024 at 03:16:58AM +0900 Masahiro Yamada wrote:
> Since commit f1d87664b82a ("kbuild: cross-compile linux-headers package
> when possible"), 'make bindeb-pkg' may attempt to cross-compile the
> linux-headers package, but it fails under certain circumstances.
>
> For example, when CONFIG_MODULE_SIG_FORMAT is enabled on Debian, the
> following command fails:
>
> $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- bindeb-pkg
> [ snip ]
> Rebuilding host programs with aarch64-linux-gnu-gcc...
> HOSTCC debian/linux-headers-6.12.0-rc4/usr/src/linux-headers-6.12.0-rc4/scripts/kallsyms
> HOSTCC debian/linux-headers-6.12.0-rc4/usr/src/linux-headers-6.12.0-rc4/scripts/sorttable
> HOSTCC debian/linux-headers-6.12.0-rc4/usr/src/linux-headers-6.12.0-rc4/scripts/asn1_compiler
> HOSTCC debian/linux-headers-6.12.0-rc4/usr/src/linux-headers-6.12.0-rc4/scripts/sign-file
> In file included from /usr/include/openssl/opensslv.h:109,
> from debian/linux-headers-6.12.0-rc4/usr/src/linux-headers-6.12.0-rc4/scripts/sign-file.c:25:
> /usr/include/openssl/macros.h:14:10: fatal error: openssl/opensslconf.h: No such file or directory
> 14 | #include <openssl/opensslconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
>
> This commit adds a new profile, pkg.linux-upstream.nokernelheaders, to
> guard the linux-headers package.
>
> There are two options to fix the above issue.
>
> [option 1] Set the pkg.linux-upstream.nokernelheaders build profile
>
> $ DEB_BUILD_PROFILES=pkg.linux-upstream.nokernelheaders \
> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- bindeb-pkg
>
> This skips the building of the linux-headers package.
>
> [option 2] Install the necessary build dependencies
>
> If you want to cross-compile the linux-headers package, you need to
> install additional packages. This is a one-time installation step.
>
> For example, on Debian, the packages necessary for cross-compiling it
> to arm64 can be installed with the following commands:
>
> # dpkg --add-architecture arm64
> # apt update
> # apt install gcc-aarch64-linux-gnu libssl-dev:arm64
>
> Fixes: f1d87664b82a ("kbuild: cross-compile linux-headers package when possible")
> Reported-by: Ron Economos <re@w6rz.net>
> Closes: https://lore.kernel.org/all/b3d4f49e-7ddb-29ba-0967-689232329b53@w6rz.net/
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> scripts/package/builddeb | 2 +-
> scripts/package/install-extmod-build | 6 ++----
> scripts/package/mkdebian | 9 ++++++++-
> 3 files changed, 11 insertions(+), 6 deletions(-)
Nice solution and thanks for also documenting option 2.
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
next prev parent reply other threads:[~2024-10-23 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 18:16 [PATCH 1/3] kbuild: rpm-pkg: disable kernel-devel package when cross-compiling Masahiro Yamada
2024-10-22 18:16 ` [PATCH 2/3] kbuild: deb-pkg: add pkg.linux-upstream.nokernelheaders build profile Masahiro Yamada
2024-10-23 13:06 ` Ron Economos
2024-10-23 14:28 ` Masahiro Yamada
2024-10-23 15:38 ` Nicolas Schier [this message]
2024-11-06 19:18 ` Matt Fleming
2024-11-09 21:53 ` Masahiro Yamada
2024-10-22 18:16 ` [PATCH 3/3] kbuild: deb-pkg: add pkg.linux-upstream.nokerneldbg " Masahiro Yamada
2024-10-23 15:39 ` Nicolas Schier
2024-10-27 18:35 ` [PATCH 1/3] kbuild: rpm-pkg: disable kernel-devel package when cross-compiling Nathan Chancellor
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=ZxkYYLbiXZ3p59iu@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=benh@debian.org \
--cc=justinstitt@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=re@w6rz.net \
/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