From: Ed Avis <eda@waniasset.com>
Date: Sun, 05 Oct 2008 09:46:57 GMT
Subject: Re: Build bug report: 'make check' needs sparse, but configure doesn't check it
Message-ID: <loom.20081005T094301-345@post.gmane.org>
In-Reply-To: <20081005003446.GN21650@dpotapov.dyndns.org>

Dmitry Potapov <dpotapov <at> gmail.com> writes:

>The whole point of 'make check' is to run 'sparce' on all files.

>If you want to build
>and to test the resulting binaries then you run 'make test'.

Thanks, I didn't realize that.  I assumed that 'make check' was to run the test
suite.

That is the convention used by most autoconf-based programs: for example if you
download coreutils then 'make check' runs the tests, so the normal way to build
and install is something like 'configure && make check && make install'.

To reduce confusion I suggest renaming the target to 'make sparse'.  Then it's
obvious what it does and it can't get confused with the more common usage of
'make check'.

-- 
Ed Avis <eda@waniasset.com>