Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: [PATCH] Makefile: use locally built sparse in the selfcheck target
Date: Thu, 9 Nov 2017 16:30:48 +0000	[thread overview]
Message-ID: <10d6a020-ebe8-6a31-e4cb-ff67c1a1009c@ramsayjones.plus.com> (raw)


Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
---

Hi Chris,

I was recently setting up a new system and didn't have sparse
installed. The 'make selfcheck' target failed ...

ATB,
Ramsay Jones

 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index d034176..d1a303e 100644
--- a/Makefile
+++ b/Makefile
@@ -18,7 +18,7 @@ LDFLAGS += -g
 LD = gcc
 AR = ar
 PKG_CONFIG = pkg-config
-CHECKER = ./cgcc -no-compile
+CHECKER = CHECK=./sparse ./cgcc -no-compile
 CHECKER_FLAGS =
 
 ALL_CFLAGS = $(CFLAGS) $(BASIC_CFLAGS)
-- 
2.15.0

             reply	other threads:[~2017-11-09 16:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 16:30 Ramsay Jones [this message]
2017-11-09 17:06 ` [PATCH] Makefile: use locally built sparse in the selfcheck target Luc Van Oostenryck
2017-11-09 17:37   ` Ramsay Jones
2017-11-09 17:43     ` Luc Van Oostenryck
2017-11-09 17:55       ` Ramsay Jones
2017-11-09 17:57         ` Christopher Li
2017-11-09 18:03         ` Ramsay Jones
2017-11-09 18:09           ` Christopher Li
2017-11-09 18:32             ` Ramsay Jones
2017-11-11 14:44               ` Luc Van Oostenryck
2017-11-09 18:32           ` Luc Van Oostenryck
2017-11-09 17:48 ` Christopher Li

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=10d6a020-ebe8-6a31-e4cb-ff67c1a1009c@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=sparse@chrisli.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