linux-kernel - Re: problem in building 4.8.0: references to non-existent util CLANG

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: <631cc19b-f8c0-7e07-a60f-fcd52e8a8564@infradead.org>
Date:   Sat, 18 Aug 2018 18:36:21 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Linda Walsh <lkml@...nx.org>,
        Linux-Kernel <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: problem in building 4.8.0: references to non-existent util CLANG

On 08/18/2018 05:48 PM, Linda Walsh wrote:
> Is CLANG required for building now?
> 
> when I did a "make xconfig" (or any make, for that matter), I get:
> 
>>  make xconfig
> scripts/kconfig/qconf  Kconfig
> invocation line: ./scripts/clang-version.sh gcc     ## debug line I added
> ./scripts/clang-version.sh: line 15: ./COPYING: Permission denied
> ./scripts/clang-version.sh: line 23: printf: __clang_major__: invalid number
> ./scripts/clang-version.sh: line 23: printf: __clang_minor__: invalid number
> ./scripts/clang-version.sh: line 23: printf: __clang_patchlevel__: invalid number
> init/Kconfig:24:warning: 'CLANG_VERSION': number is invalid
> .config:50:warning: symbol value '00000' invalid for CLANG_VERSION
> 
> The reference to COPYING comes from me running make in the
> top dir, where there is a text file named COPYING, however it is
> not executable.
> 
> I put in an echo to see what command line the script was being passed,
> "gcc"?
> 
> I'm guessing but I don't think the clang script should be getting
> called at all.  I installed the sources by patching 4.17.0 (done via a
> script).
> 
> Are there instructions somewhere for what command(s) to run for patching?
> It seems to have changed from using the standard patch program to using
> a git version that isn't compatible w/the gnu version.  I adapted the
> script to the git version and that's seemed to work since I did
> the change.  But with 4.18.0, I am uncertain if it is working correctly.
> 
> If the above was the only problem, I'd be less concerned, but
> scripts run after the main build to build external modules failed.
> It seems unlikely the two problems are related, but I wanted to fix
> this first before going on to the compile-fails.
> 
> Please Cc me, as I'm not currently on the list.
> 
> Thanks,
> Linda W.
> 

Looks like this patch should fix it:
https://marc.info/?l=linux-kbuild&m=153447099313149&w=2



-- 
~Randy