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
Shawn O. Pearce <spearce@spearce.org>
Date
Oct 6, 2008, 06:58 UTC
Message-ID
<20081006065847.GA27516@spearce.org>
In-Reply-To
<loom.20081005T094301-345@post.gmane.org>
Ed Avis <eda@waniasset.com> wrote:
Show 10 quoted lines
> 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'.
> 
> 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'.

Nah. We're not going to rename the target to "make sparse". First off that sounds like we are compiling the sparse binary for the user, and we will never do that. And existing developers who use "make check" to run sparse are used to that calling convention.

-- 
Shawn.
Previous: Ed AvisNext: Ed Avis
Message 4 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.