From: Kees Cook <kees@kernel.org>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Build error in next-20260223 gcc-plugins/latent_entropy_plugin.so
Date: Tue, 24 Feb 2026 23:33:32 -0800 [thread overview]
Message-ID: <202602242333.24E5CB214@keescook> (raw)
In-Reply-To: <4051116.1771996801@turing-police>
On Wed, Feb 25, 2026 at 12:20:01AM -0500, Valdis Klētnieks wrote:
> Building next-20260223 dies an early death:
>
> HOSTLD arch/x86/tools/relocs
> HOSTCC arch/x86/tools/vdso2c
> HOSTCXX scripts/gcc-plugins/latent_entropy_plugin.so
> In file included from scripts/gcc-plugins/latent_entropy_plugin.c:78:
> scripts/gcc-plugins/gcc-common.h: In function 'void debug_tree(const_tree)':
> scripts/gcc-plugins/gcc-common.h:417:20: error: 'CONST_CAST_TREE' was not declared in this scope; did you mean 'CONST_CAST_EXPR'?
> 417 | debug_tree(CONST_CAST_TREE(t));
> | ^~~~~~~~~~~~~~~
> | CONST_CAST_EXPR
> scripts/gcc-plugins/gcc-common.h: In function 'void debug_gimple_stmt(const_gimple_ptr)':
> scripts/gcc-plugins/gcc-common.h:312:47: error: expected primary-expression before ',' token
> 312 | #define CONST_CAST_GIMPLE(X) CONST_CAST(gimple, (X))
> | ^
> scripts/gcc-plugins/gcc-common.h:422:27: note: in expansion of macro 'CONST_CAST_GIMPLE'
> 422 | debug_gimple_stmt(CONST_CAST_GIMPLE(s));
> | ^~~~~~~~~~~~~~~~~
> scripts/gcc-plugins/gcc-common.h:312:30: error: 'CONST_CAST' was not declared in this scope; did you mean 'CONST_INT'?
> 312 | #define CONST_CAST_GIMPLE(X) CONST_CAST(gimple, (X))
> | ^~~~~~~~~~
> scripts/gcc-plugins/gcc-common.h:422:27: note: in expansion of macro 'CONST_CAST_GIMPLE'
> 422 | debug_gimple_stmt(CONST_CAST_GIMPLE(s));
> | ^~~~~~~~~~~~~~~~~
> make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/latent_entropy_plugin.so] Error 1
> make[2]: *** [scripts/Makefile.build:546: scripts/gcc-plugins] Error 2
> make[1]: *** [/usr/src/linux-next/Makefile:1316: scripts] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
>
> 'git blame' isn't showing any recent changes..
>
> next-20260109 built OK. Any ideas before I start bisecting in more detail?
>
> ????????
Which GCC version?
--
Kees Cook
next prev parent reply other threads:[~2026-02-25 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 5:20 Build error in next-20260223 gcc-plugins/latent_entropy_plugin.so Valdis Klētnieks
2026-02-25 7:33 ` Kees Cook [this message]
2026-02-25 15:14 ` Valdis Klētnieks
2026-03-14 13:50 ` Ingo Saitz
2026-03-14 14:44 ` Ingo Saitz
2026-03-20 19:23 ` Kees Cook
2026-03-21 12:25 ` Ingo Saitz
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=202602242333.24E5CB214@keescook \
--to=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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