From: Kees Cook <kees@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org
Subject: how to create early build deps?
Date: Wed, 16 Apr 2025 19:55:02 -0700 [thread overview]
Message-ID: <202504161928.17A90D9B@keescook> (raw)
Hi!
I am stumped...
I swear there was a time when changing the gcc-plugins would trigger a
full rebuild of all kernel sources. I tried to bisect where that stopped
happening, but it went back far enough that things stopped building with
my compiler at all. ;)
Anyway, I need this also for the Clang randstruct seed file -- if it
changes, we need to rebuild everything. I thought this worked back in
v5.19 when I moved the randstruct seed generation into scripts/basic[1],
but regenerating it doesn't trigger a rebuild (with v5.19 nor current
Linus nor linux-next):
$ make O=clang-all LLVM=1 allmodconfig kernel/seccomp.o
make[1]: Entering directory '/srv/code/clang-all'
...
GENSEED scripts/basic/randstruct.seed
...
CC kernel/seccomp.o
make[1]: Leaving directory '/srv/code/clang-all'
$ rm clang-all/scripts/basic/randstruct.seed
$ make O=clang-all LLVM=1 kernel/seccomp.o
make[1]: Entering directory '/srv/code/clang-all'
GEN Makefile
GENSEED scripts/basic/randstruct.seed
DESCEND objtool
CALL ../scripts/checksyscalls.sh
INSTALL libsubcmd_headers
make[1]: Leaving directory '/srv/code/clang-all'
kernel/seccomp.o doesn't get rebuilt :(
By what mechanism can I convince kbuild to rebuild everything if
randstruct.seed (or the gcc-plugins) are changed?
Thanks!
-Kees
[1] be2b34fa9be3 ("randstruct: Move seed generation into scripts/basic/")
--
Kees Cook
next reply other threads:[~2025-04-17 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 2:55 Kees Cook [this message]
2025-04-25 8:25 ` how to create early build deps? Nicolas Schier
2025-04-29 12:49 ` Nicolas Schier
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=202504161928.17A90D9B@keescook \
--to=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.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