From: Brian Norris <briannorris@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-kbuild@vger.kernel.org,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: possible dependency error?
Date: Mon, 1 Jul 2024 17:37:07 -0700 [thread overview]
Message-ID: <ZoNLs_9nFHvm6Nqw@google.com> (raw)
In-Reply-To: <CAK7LNAT9n9cQ_5mZ6rE+VD-KwOQm_Rjq=Q-Cx7ib+bSqmbbubA@mail.gmail.com>
Hi,
On Wed, Jun 19, 2024 at 03:02:35PM +0900, Masahiro Yamada wrote:
> I do not see any maintainer for tools/build/, but at least
> you can find who is picking up the patches.
>
>
> masahiro@zoe:~/ref/linux(master)$ ./scripts/get_maintainer.pl -f tools/build/
Thanks. I've factored some of this into my addressee list.
> OK, you bypassed fixdep for fixdep itself.
>
> fixdep will not be rebuilt when the command line changes,
> but it may not be a big deal.
> It is not working that way already.
Yeah, that was one rough edge. I didn't manage to smooth that one out,
but like you say, it's not really much of a regression. (It *can* work
today sometimes for just the right kind of incremental build, because
you may have a pre-existing fixdep laying around that will be used if
available. But it's not really *correct* still.)
> BTW, did you have a chance to test your code
> with the -j<N> option?
>
>
> I quickly tested your change, and I observed new
> "jobserver unavailable" warnings.
>
>
> masahiro@zoe:~/ref/linux(master)$ make -j24
> mkdir -p /home/masahiro/ref/linux/tools/objtool && make
> O=/home/masahiro/ref/linux subdir=tools/objtool --no-print-directory
> -C objtool
> make[4]: warning: jobserver unavailable: using -j1. Add '+' to parent
> make rule.
> make[5]: warning: jobserver unavailable: using -j1. Add '+' to parent
> make rule.
>
>
>
> The first line:
>
> mkdir -p /home/masahiro/ref/linux/tools/objtool && make
> O=/home/masahiro/ref/linux subdir=tools/objtool --no-print-directory
> -C objtool
>
> is an existing noise regardless of your change.
> (I do not know if anybody cares about this either)
Thanks. I tried to tackle the existing and new noise in my posting here:
Subject: [PATCH 0/3] tools build: Incorrect fixdep dependencies
https://lore.kernel.org/lkml/20240702003119.3641219-1-briannorris@chromium.org/
Hopefully that's not horribly off the mark, although I'll admit tools/
is a bit of unfamiliar territory.
Brian
prev parent reply other threads:[~2024-07-02 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 23:27 possible dependency error? Bjorn Helgaas
2023-05-18 8:26 ` Masahiro Yamada
2024-05-23 17:54 ` Brian Norris
2024-05-25 16:35 ` Masahiro Yamada
2024-06-18 23:29 ` Brian Norris
2024-06-19 6:02 ` Masahiro Yamada
2024-07-02 0:37 ` Brian Norris [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=ZoNLs_9nFHvm6Nqw@google.com \
--to=briannorris@chromium.org \
--cc=helgaas@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=peterz@infradead.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