All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Progyan Bhattacharya <bprogyan@gmail.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re[v2]: Use of GCC plugin instead ISO C
Date: Tue, 6 Mar 2018 09:24:12 -0800	[thread overview]
Message-ID: <d3ce60f9-7838-a98b-c807-fa0603544f9d@infradead.org> (raw)
In-Reply-To: <1520342938.6596.1.camel@acm.org>

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

  reply	other threads:[~2018-03-06 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18  8:06 Use of GCC plugin instead ISO C Progyan Bhattacharya
2018-02-18 16:47 ` Randy Dunlap
2018-02-22 14:37   ` Progyan Bhattacharya
2018-03-01  7:50     ` Re[v2]: " Progyan Bhattacharya
2018-03-01 21:42       ` Randy Dunlap
2018-03-06 13:28         ` Progyan Bhattacharya
2018-03-06 17:24           ` Randy Dunlap [this message]
2018-03-07  6:01             ` Progyan Bhattacharya
2018-03-07 17:36               ` Randy Dunlap

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=d3ce60f9-7838-a98b-c807-fa0603544f9d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bprogyan@gmail.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.