I was surprised to see only one major flaw in the new test driver code
in the EXEEXT treatment, testing it for the first time now: inference
rules
.chk.log:
...
will not cause `make' to consider foo.chk.exe as a valid prerequisite to
foo.log (there is no problem with explicit rules like
* Ralf Wildenhues wrote on Sat, Apr 04, 2009 at 12:16:32PM CEST:
> + - In 1.10b, the `parallel-tests' driver introduced per-extension test
> +driver variables `_LOG_COMPILER', defined as
> +
> + $(_LOG_COMPILE) $(AM__LOG_FLAGS) $(_LOG_FLAGS)
> +
> +for extensions `.ext' registered in
* Akim Demaille wrote on Mon, Mar 30, 2009 at 10:02:51PM CEST:
> Le 30 mars 09 à 21:37, Ralf Wildenhues a écrit :
>> I mean with
>> TESTS = foo bar.test baz.chk
>> TEST_EXTENSIONS = .chk
>>
>> then foo.log and bar.test.log (sic!) will be generated using explicit
>> rules, while baz.log will be ge
After ad-parallel-tests and master were merged into next (see the other
two mails), I applied these patches before tagging 1.10b:
1) Update AM_RECURSIVE_TARGETS for parallel-tests.
This is obvious and can really be considered as part of the merge, as
AM_RECURSIVE_TARGETS was introduced on master w
Hello,
there were some patches I pushed to the master, ad-parallel-tests, and
next branches before creating 1.10b, which I haven't posted on this list
yet. I would like to do this now, before going on.
The following is the only remaining patch pushed to ad-parallel-tests,
to implement recheck-ht
remaining patches applied to master last weekend, before master was
merged into next:
1) update of imported files (patch not shown)
2) fixing an overfull hbox in the manual (yes, we are latex warning
free! ;-)
3) maintainer-check need not warn about using DESTDIR=... as argument to
`make': we pr
