From: Tan Nayir <tannayir@gmail.com>
To: irogers@google.com
Cc: acme@kernel.org, andrii@kernel.org, eranian@google.com,
jolsa@kernel.org, jpoimboe@kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
masahiroy@kernel.org, namhyung@kernel.org, nathan@kernel.org,
ndesaulniers@google.com, nicolas@fjasle.eu, peterz@infradead.org,
trix@redhat.com
Subject: Re: [PATCH v4 3/3] objtool: Alter how HOSTCC is forced
Date: Sun, 21 Apr 2024 00:43:26 +0200 [thread overview]
Message-ID: <d8b36823-4247-49d4-8de5-d06ea5d85e80@gmail.com> (raw)
In-Reply-To: <20230126190606.40739-4-irogers@google.com>
Could this patch be backported to LTS branches? Entire build fails if
KBUILD_HOSTCFLAGS has flags that would make the libsubcmd incompatible
with the built objtool, since those flags were not passed to libsubcmd
before this patch.
One example is that the AOSP GKI builds fail since they set a custom
sysroot using that variable. For the Google devs, issue b/335829879 is
relevant.
next prev parent reply other threads:[~2024-04-20 22:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 19:06 [PATCH v4 0/3] objtool build improvements Ian Rogers
2023-01-26 19:06 ` [PATCH v4 1/3] objtool: Install libsubcmd in build Ian Rogers
2023-02-01 16:26 ` [tip: objtool/core] " tip-bot2 for Ian Rogers
2023-01-26 19:06 ` [PATCH v4 2/3] objtool: Properly support make V=1 Ian Rogers
2023-02-01 16:26 ` [tip: objtool/core] " tip-bot2 for Ian Rogers
2023-01-26 19:06 ` [PATCH v4 3/3] objtool: Alter how HOSTCC is forced Ian Rogers
2023-02-01 16:26 ` [tip: objtool/core] objtool: Fix HOSTCC flag usage tip-bot2 for Ian Rogers
2023-02-01 17:02 ` Mark Rutland
2023-02-01 17:36 ` Josh Poimboeuf
2023-02-03 18:25 ` Vladimir Oltean
2023-02-04 17:05 ` Josh Poimboeuf
2023-02-04 21:21 ` Ian Rogers
2023-02-04 10:17 ` tip-bot2 for Ian Rogers
2024-04-20 22:43 ` Tan Nayir [this message]
2023-01-26 19:34 ` [PATCH v4 0/3] objtool build improvements Josh Poimboeuf
2023-01-31 0:25 ` Josh Poimboeuf
2023-01-31 0:31 ` Ian Rogers
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=d8b36823-4247-49d4-8de5-d06ea5d85e80@gmail.com \
--to=tannayir@gmail.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=peterz@infradead.org \
--cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).