[FYI] {maint} cosmetics: fix a botched comment in a maintainer check

* Makefile.am (sc_tests_make_without_am_makeflags): Adjust botched description of this check. --- Makefile.am |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/Makefile.am b/Makefile.am index b9166db..06b3396 100644 --- a/Makefile.am +++ b/Makefile.am @@ -397,7 +397,8 @@ s

[PATCH 4/6] test defs: allow compilers to be auto-selected on user's request

In the recent changes, by pre-setting the required compilers for the `configure' scripts launched by the test scripts, we have slightly reduced the coverage of autoconf/automake code aimed at automatically detecting said compilers. This commit restore such coverage, by allowing the user to instruc

[PATCH 6/6] readme: how to run the testsuite with cross-compilers

* tests/README: Suggest a better way to run the automake testsuite with cross-compilers -- that is, configuring the Automake source tree with proper `--build' and `--host' configure option. And yes, specifying both these options (not only `--host') is indeed required to avoid spurious failures in

[PATCH 3/6] test defs: substitute compilers and flags found at configure time

* tests/Makefile.am (do_subst): Also substitute CC, CXX, F77, FC, CPPFLAGS, CFLAGS, CXXFLAGS, FCFLAGS and FFLAGS. * tests/defs-static.in: Define those variables, allowing for overrides from the environment. * tests/defs (for tool in $required): Export (subsets of) those variables when the stuff in

[PATCH 1/6] configure: search generic compilers for use in the tests

* configure.ac: Look for "generic" C, C++ and Fortran compilers, with the aim of starting to use them in the testsuite (this will be done in future changes). This is more tricky than it seems, since we don't want to abort the whole configure script even if no one of those compilers is available (a

[PATCH 0/6] Merge 'experimental/compilers-for-testsuite' into master

I think this series is now polished enough to be merged from the branch 'experimental/compilers-for-testsuite' into master proper. Some improvements are still possible and advisable (for example, looking for gcc, g++ etc. at configure time rather than at testsuite time, which should make testing i

[PATCH 5/6] tests: no need to unset CFLAGS in tests requiring 'gcc' anymore

* tests/ccnoco.test: Since this test have "gcc" in $required, there is no need to manually nullify the CFLAGS variable, since now `tests/defs' should automatically re-define that to a value appropriate for gcc. * tests/ccnoco3.test: Likewise. --- tests/ccnoco.test |4 tests/ccnoco3.test

[PATCH 2/6] test defs: setup `*FLAGS' variables for GNU compilers

* configure.ac: Setup some `*FLAGS' variables for use by the GNU compilers in our testsuite. For example, use `GNU_CFLAGS' instead of `CFLAGS', and so on for similar variables. This is especially useful in case the compilers found or defined at configure time are not the GNU ones. * tests/defs-st