From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, llvm@lists.linux.dev,
bpf@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: Apply 13e07691a16f and co. to linux-6.1.y
Date: Fri, 8 Sep 2023 17:52:31 +0100 [thread overview]
Message-ID: <2023090821-octopus-unreal-87a2@gregkh> (raw)
In-Reply-To: <20230908161526.GA3344687@dev-arch.thelio-3990X>
On Fri, Sep 08, 2023 at 09:15:26AM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
>
> Please consider applying the following commits to 6.1 (they all picked
> cleanly for me):
>
> 630ae80ea1dd ("tools lib subcmd: Add install target")
> 77dce6890a2a ("tools lib subcmd: Make install_headers clearer")
> 5d890591db6b ("tools lib subcmd: Add dependency test to install_headers")
> 0e43662e61f2 ("tools/resolve_btfids: Use pkg-config to locate libelf")
> af03299d8536 ("tools/resolve_btfids: Install subcmd headers")
> 13e07691a16f ("tools/resolve_btfids: Alter how HOSTCC is forced")
> 56a2df7615fa ("tools/resolve_btfids: Compile resolve_btfids as host program")
> e0975ab92f24 ("tools/resolve_btfids: Tidy HOST_OVERRIDES")
> 2531ba0e4ae6 ("tools/resolve_btfids: Pass HOSTCFLAGS as EXTRA_CFLAGS to prepare targets")
> edd75c802855 ("tools/resolve_btfids: Fix setting HOSTCFLAGS")
>
> The most critical change is 13e07691a16f, which resolves a missing
> EXTRA_CFLAGS to the libsubcmd build. Without that EXTRA_CFLAGS, the
> Android hermetic toolchain kernel build fails on host distributions
> using glibc 2.38 and newer. The majority of those commits are strictly
> needed due to dependency/fixes requirements, the few that are not still
> seem to be worth bringing in for ease of backporting the rest and do not
> appear to cause any problems.
>
> I proposed another solution downstream, which may be more palatable if
> people have concerns about this list of changes and the risk of
> regressions, but Ian seemed to have some concerns on that thread around
> that path and suggested this series of backports instead:
>
> https://android-review.googlesource.com/c/kernel/common/+/2745896
>
> While the number of patches seems large, the final changes are pretty
> well self-contained.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-09-08 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 16:15 Apply 13e07691a16f and co. to linux-6.1.y Nathan Chancellor
2023-09-08 16:52 ` Greg Kroah-Hartman [this message]
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=2023090821-octopus-unreal-87a2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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