From: Brian Norris <briannorris@chromium.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org,
Brian Norris <briannorris@chromium.org>
Subject: [PATCH v2 0/3] tools build: Incorrect fixdep dependencies
Date: Tue, 2 Jul 2024 14:58:36 -0700 [thread overview]
Message-ID: <20240702215854.408532-1-briannorris@chromium.org> (raw)
Hi all,
The following series consists of a few bugfixes on the topic of "misuse
of fixdep in the tools/ build tree." There is no listed maintainer for
tools/build, but there are for tools/bpf and tools/objtool, which are
the main pieces that affect most users, because they're built as part of
the main kernel build. I've addressed this series to a selection of
those maintainers, and those that have previously applied build changes
in tools/. I hope one of you can apply this series, pending favorable
review. Or feel free to point me to a different set of maintainers.
This patch series came out of poking around some build errors seen by me
and my coworkers, and I found that there were rather similar reports a
while back here:
Subject: possible dependency error?
https://lore.kernel.org/all/ZGVi9HbI43R5trN8@bhelgaas/
I reported some findings to that thread; see also subsequent discussion:
https://lore.kernel.org/all/Zk-C5Eg84yt6_nml@google.com/
One element of that discussion: these problems are already solved
consistently in Kbuild. tools/build purposely borrows some from Kbuild,
but also purposely does not actually use Kbuild. While it'd make my life
easier if tools/ would just adopt Kbuild (at least for the tools which
are built during kernel builds), I've chosen a path that I hope will
yield less resistance -- simply hacking up the existing tools/ build
without major changes to its design.
NB: I've also CC'd Kbuild folks, since Masahiro has already been so
helpful here, but note that this is not really a "kbuild" patch series.
Regards,
Brian
Changes in v2:
- also fix libbpf shared library rules
- ensure OUTPUT is always set in lib/bpf, and always an absolute path
- add backup $(Q) definition in tools/build/Makefile.include
Brian Norris (3):
tools build: Correct libsubcmd fixdep dependencies
tools build: Avoid circular .fixdep-in.o.cmd issues
tools build: Correct bpf fixdep dependencies
tools/build/Makefile | 11 ++---------
tools/build/Makefile.include | 12 +++++++++++-
tools/lib/bpf/Makefile | 14 ++++++++++++--
tools/lib/subcmd/Makefile | 2 +-
4 files changed, 26 insertions(+), 13 deletions(-)
--
2.45.2.803.g4e1b14247a-goog
next reply other threads:[~2024-07-02 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 21:58 Brian Norris [this message]
2024-07-02 21:58 ` [PATCH v2 1/3] tools build: Correct libsubcmd " Brian Norris
2024-07-03 14:43 ` Jiri Olsa
2024-07-02 21:58 ` [PATCH v2 2/3] tools build: Avoid circular .fixdep-in.o.cmd issues Brian Norris
2024-07-03 14:43 ` Jiri Olsa
2024-07-02 21:58 ` [PATCH v2 3/3] tools build: Correct bpf fixdep dependencies Brian Norris
2024-07-03 14:47 ` Jiri Olsa
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=20240702215854.408532-1-briannorris@chromium.org \
--to=briannorris@chromium.org \
--cc=acme@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.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®