linux-kernel - Re: Re[v2]: Use of GCC plugin instead ISO C

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: <d3ce60f9-7838-a98b-c807-fa0603544f9d@infradead.org>
Date:   Tue, 6 Mar 2018 09:24:12 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Progyan Bhattacharya <bprogyan@...il.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Re[v2]: Use of GCC plugin instead ISO C

On 03/06/2018 05:28 AM, Progyan Bhattacharya wrote:
> On Thu, 2018-03-01 at 13:42 -0800, Randy Dunlap wrote:
>> If you would build with V=1 and capture all of the output (lots of
>> it!) to a file,
>> you could search it for "pedantic" to see where/why it is used.
>>
>> I have no idea about the permission problem that you quoted above.
> 
> Sorry for the misunderstanding!
> Here is the full build log for
> 
>     make V=1
> 

Thanks. I don't see a problem there except for the final line.

First, please make sure that this file does not already exist before starting
a build:  /home/progyan/Programs/Linux/tools/objtool/.objtool-in.o.cmd


Then I will look at this more if you will send me your kernel .config file and
the exact command(s) that you use to run the build.

thanks,
-- 
~Randy