From: Dave Jones <davej@redhat.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, sam@ravnborg.org
Subject: Re: $CHECK can't be overridden
Date: Thu, 22 Mar 2007 01:37:14 -0400 [thread overview]
Message-ID: <20070322053714.GE17159@redhat.com> (raw)
In-Reply-To: <12464.1174541199@kao2.melbourne.sgi.com>
On Thu, Mar 22, 2007 at 04:26:39PM +1100, Keith Owens wrote:
> Dave Jones (on Thu, 22 Mar 2007 01:15:25 -0400) wrote:
> >make help implies that supplying $CHECK on the command line
> >should override sparse as the checker used when building with C=1
> >Yet, this doesn't seem to be the case.
> >
> >This would be useful for cases where for eg, sparse isn't in
> >the $PATH, allowing an explicit path to the executable to be
> >passed in automated build environments.
>
> Works for me.
>
> # make C=1 CHECK=foo
Ah, my bad. I was thinking it was an environment var rather
than a makefile var. I was using 'CHECK=foo make bzImage C=1'
Thanks,
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-22 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 5:15 $CHECK can't be overridden Dave Jones
2007-03-22 5:26 ` Keith Owens
2007-03-22 5:37 ` Dave Jones [this message]
2007-03-22 5:43 ` Keith Owens
2007-03-22 7:30 ` Al Viro
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=20070322053714.GE17159@redhat.com \
--to=davej@redhat.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox