git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Build bug report: 'make check' needs sparse, but configure doesn't check it

From
EAEd Avis <eda@waniasset.com>
Date
Oct 5, 2008, 09:46 UTC
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>
Previous: Dmitry PotapovNext: Shawn O. Pearce
Message 3 of 5 in “Build bug report: 'make check' needs sparse, but configure doesn't check it”
  1. Ed AvisOct 4, 2008
  2. Dmitry PotapovOct 5, 2008
  3. Ed AvisOct 5, 2008
  4. Shawn O. PearceOct 6, 2008
  5. Ed AvisOct 6, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.