From: Jiri Olsa <olsajiri@gmail.com>
To: Brian Norris <briannorris@chromium.org>
Cc: 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>,
Masahiro Yamada <masahiroy@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 2/3] tools build: Avoid circular .fixdep-in.o.cmd issues
Date: Wed, 3 Jul 2024 16:43:28 +0200 [thread overview]
Message-ID: <ZoVjkIG83Bk2QWPE@krava> (raw)
In-Reply-To: <20240702215854.408532-3-briannorris@chromium.org>
On Tue, Jul 02, 2024 at 02:58:38PM -0700, Brian Norris wrote:
> The 'fixdep' tool is used to post-process dependency files for various
> reasons, and it runs after every object file generation command. This
> even includes 'fixdep' itself.
>
> In Kbuild, this isn't actually a problem, because it uses a single
> command to generate fixdep (a compile-and-link command on fixdep.c), and
> afterward runs the fixdep command on the accompanying .fixdep.cmd file.
>
> In tools/ builds (which notably is maintained separately from Kbuild),
> fixdep is generated in several phases:
>
> 1. fixdep.c -> fixdep-in.o
> 2. fixdep-in.o -> fixdep
>
> Thus, fixdep is not available in the post-processing for step 1, and
> instead, we generate .cmd files that look like:
>
> ## from tools/objtool/libsubcmd/.fixdep.o.cmd
> # cannot find fixdep (/path/to/linux/tools/objtool/libsubcmd//fixdep)
> [...]
>
> These invalid .cmd files are benign in some respects, but cause problems
> in others (such as the linked reports).
>
> Because the tools/ build system is rather complicated in its own right
> (and pointedly different than Kbuild), I choose to simply open-code the
> rule for building fixdep, and avoid the recursive-make indirection that
> produces the problem in the first place.
>
> Link: https://lore.kernel.org/all/Zk-C5Eg84yt6_nml@google.com/
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> ---
>
> (no changes since v1)
>
> tools/build/Makefile | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/tools/build/Makefile b/tools/build/Makefile
> index 17cdf01e29a0..fea3cf647f5b 100644
> --- a/tools/build/Makefile
> +++ b/tools/build/Makefile
> @@ -43,12 +43,5 @@ ifneq ($(wildcard $(TMP_O)),)
> $(Q)$(MAKE) -C feature OUTPUT=$(TMP_O) clean >/dev/null
> endif
>
> -$(OUTPUT)fixdep-in.o: FORCE
> - $(Q)$(MAKE) $(build)=fixdep
> -
> -$(OUTPUT)fixdep: $(OUTPUT)fixdep-in.o
> - $(QUIET_LINK)$(HOSTCC) $(KBUILD_HOSTLDFLAGS) -o $@ $<
> -
> -FORCE:
> -
> -.PHONY: FORCE
> +$(OUTPUT)fixdep: $(srctree)/tools/build/fixdep.c
> + $(QUIET_CC)$(HOSTCC) $(KBUILD_HOSTLDFLAGS) -o $@ $<
ok, looks like that will make things easier, also we won't need tools/build/Build
thanks,
jirka
next prev parent reply other threads:[~2024-07-03 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 21:58 [PATCH v2 0/3] tools build: Incorrect fixdep dependencies Brian Norris
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 [this message]
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=ZoVjkIG83Bk2QWPE@krava \
--to=olsajiri@gmail.com \
--cc=acme@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=briannorris@chromium.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