linux-kernel - Toolchain-dependent config options

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210113222112.ej4rrd5xw2pwegvw@treble>
Date:   Wed, 13 Jan 2021 16:21:12 -0600
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Toolchain-dependent config options

Hi Masahiro,

If I copy a config with CONFIG_GCC_PLUGINS to another system which
doesn't have the gcc-plugin-devel package, it gets silently disabled by
"make olddefconfig".

I've seen multiple cases lately where this is causing confusion.  I
suspect the problem is getting worse with recent added support for a
variety of toolchains and toolchain-dependent features.

Would it be possible to have an error (or at least a warning) in this
case?

For example, a "depends-error" which triggers an error if its failure
would disable a feature?

-- 
Josh