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 1/3] tools build: Correct libsubcmd fixdep dependencies
Date: Wed, 3 Jul 2024 16:43:56 +0200 [thread overview]
Message-ID: <ZoVjrDMg1XM840tT@krava> (raw)
In-Reply-To: <20240702215854.408532-2-briannorris@chromium.org>
On Tue, Jul 02, 2024 at 02:58:37PM -0700, Brian Norris wrote:
> All built targets need fixdep to be built first, before handling object
> dependencies [1]. We're missing one such dependency before the libsubcmd
> target.
>
> This resolves .cmd file generation issues such that the following
> sequence produces many fewer results:
>
> $ git clean -xfd tools/
> $ make tools/objtool
> $ grep "cannot find fixdep" $(find tools/objtool -name '*.cmd')
>
> In particular, only a buggy tools/objtool/libsubcmd/.fixdep.o.cmd
> remains, due to circular dependencies of fixdep on itself.
>
> Such incomplete .cmd files don't usually cause a direct problem, since
> they're designed to fail "open", but they can cause some subtle problems
> that would otherwise be handled by proper fixdep'd dependency files.
>
> [1] This problem is better described in commit abb26210a395 ("perf
> tools: Force fixdep compilation at the start of the build"). I don't
> apply its solution here, because additional recursive make can be a bit
> of overkill.
>
> Link: https://lore.kernel.org/all/ZGVi9HbI43R5trN8@bhelgaas/
> Link: https://lore.kernel.org/all/Zk-C5Eg84yt6_nml@google.com/
> Signed-off-by: Brian Norris <briannorris@chromium.org>
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
> ---
>
> (no changes since v1)
>
> tools/lib/subcmd/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/lib/subcmd/Makefile b/tools/lib/subcmd/Makefile
> index b87213263a5e..59b09f280e49 100644
> --- a/tools/lib/subcmd/Makefile
> +++ b/tools/lib/subcmd/Makefile
> @@ -76,7 +76,7 @@ include $(srctree)/tools/build/Makefile.include
>
> all: fixdep $(LIBFILE)
>
> -$(SUBCMD_IN): FORCE
> +$(SUBCMD_IN): fixdep FORCE
> @$(MAKE) $(build)=libsubcmd
>
> $(LIBFILE): $(SUBCMD_IN)
> --
> 2.45.2.803.g4e1b14247a-goog
>
>
next prev parent reply other threads:[~2024-07-03 14:44 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 [this message]
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=ZoVjrDMg1XM840tT@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.