linux-hardening - Re: [PATCH] scripts/gcc-plugins: consistently use HOSTCC

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <163243252379.3933826.2645114887075876479.b4-ty@chromium.org>
Date:   Thu, 23 Sep 2021 14:28:49 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Ross Burton <ross.burton@....com>, linux-kernel@...r.kernel.org,
        linux-hardening@...r.kernel.org
Cc:     Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH] scripts/gcc-plugins: consistently use HOSTCC

On Thu, 23 Sep 2021 16:28:11 +0100, Ross Burton wrote:
> The GCC plugins are built using HOSTCC, but the path to the GCC plugins
> headers is obtained using CC.  This can lead to interesting failures if
> the host compiler and cross compiler are different versions, and the
> host compiler uses the cross headers.

(I changed this from HOSTCC to HOSTCXX to match the other invocations.)

Applied to for-next/gcc-plugins, thanks!

[1/1] scripts/gcc-plugins: consistently use HOSTCC
      https://git.kernel.org/kees/c/ef5ecb129791

-- 
Kees Cook