From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: NeilBrown <neilb@suse.de>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] Allow to check mdadm with clangs static checker (scan-build)
Date: Tue, 21 Jan 2014 18:39:56 +0100 [thread overview]
Message-ID: <52DEB0EC.5070103@fastmail.fm> (raw)
In-Reply-To: <20140121100643.0ebaf13d@notabene.brown>
On 01/21/2014 12:06 AM, NeilBrown wrote:
> On Mon, 20 Jan 2014 17:14:12 +0100 Bernd Schubert
> <bernd.schubert@fastmail.fm> wrote:
>
>> Clangs scan-build tool (static checker) set the environmental variable CC,
>> so Makefile should allow to use that value.
>>
>> Signed-off-by: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
>> ---
>> Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Makefile b/Makefile
>> index 043bcea..63cc3ac 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -41,7 +41,7 @@ KLIBC=/home/src/klibc/klibc-0.77
>>
>> KLIBC_GCC = gcc -nostdinc -iwithprefix include -I$(KLIBC)/klibc/include -I$(KLIBC)/linux/include -I$(KLIBC)/klibc/arch/i386/include -I$(KLIBC)/klibc/include/bits32
>>
>> -CC = $(CROSS_COMPILE)gcc
>> +CC ?= $(CROSS_COMPILE)gcc
>> CXFLAGS ?= -ggdb
>> CWFLAGS = -Wall -Werror -Wstrict-prototypes -Wextra -Wno-unused-parameter
>> ifdef WARN_UNUSED
>
> I'm not exactly against this, but presumably you could tell scan-build to run
>
> make CC=$CC
>
> to achieve the same effect with no patch ??
>
> i.e.
>
> scan-build 'make CC=$CC'
Yeah, that would also work. IMHO, it is just not very intuitive.
Maybe I should submit a patch for the man page of the debian package and
upstream docs.
>
> But maybe I'll apply it anyway.
Would be great.
Thanks,
Bernd
prev parent reply other threads:[~2014-01-21 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 16:14 [PATCH] Allow to check mdadm with clangs static checker (scan-build) Bernd Schubert
2014-01-20 23:06 ` NeilBrown
2014-01-21 17:39 ` Bernd Schubert [this message]
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=52DEB0EC.5070103@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).