From: Matt Fleming <matt@readmodwrite.com>
To: nicolas@fjasle.eu
Cc: benh@debian.org, justinstitt@google.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, masahiroy@kernel.org, morbo@google.com,
nathan@kernel.org, ndesaulniers@google.com, re@w6rz.net,
kernel-team@cloudflare.com
Subject: Re: [PATCH 2/3] kbuild: deb-pkg: add pkg.linux-upstream.nokernelheaders build profile
Date: Wed, 6 Nov 2024 19:18:46 +0000 [thread overview]
Message-ID: <20241106191846.2079521-1-matt@readmodwrite.com> (raw)
In-Reply-To: <ZxkYYLbiXZ3p59iu@fjasle.eu>
Hey there,
Can you explain how this change works a bit more? This reads like it's now
impossible to build the debian linux-headers package with clang? At Cloudflare,
we're using a custom build of gcc, not the gcc-x86-64-linux-gnu package, and
with this change we can no longer build linux-headers.
What's the solution for those of us that want to build the linux-headers deb
package but can't install gcc-*-linux-gnu?
next prev parent reply other threads:[~2024-11-06 19:18 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
2024-11-06 19:18 ` Matt Fleming [this message]
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=20241106191846.2079521-1-matt@readmodwrite.com \
--to=matt@readmodwrite.com \
--cc=benh@debian.org \
--cc=justinstitt@google.com \
--cc=kernel-team@cloudflare.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=nicolas@fjasle.eu \
--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