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@xxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
