bug#26033: EXEEXT not exported to tests

2017-03-09 Thread Peter Selinger
=?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= wrote: > > Am 08.03.2017 um 20:52 schrieb Peter Selinger: > > > The tests require this information, for > > example when they are shell scripts starting up executable programs > > to be tested. > > Not really. On the pl

bug#26033: EXEEXT not exported to tests

2017-03-08 Thread Peter Selinger
This bug is distinct from #26031 that I just reported. Summary: "make check" does not export the value of $(EXEEXT) to individual tests when they are run. The tests require this information, for example when they are shell scripts starting up executable programs to be tested. To reprodu

bug#26031: EXEEXT not working with "make check"

2017-03-08 Thread Peter Selinger
Summary: "make check" does not respect $(EXEEXT) To reproduce: = Please see the attached minimal package testing-0.0.tar.gz This succeeds: $ ./configure $ make check This also succeeds: $ ./configure ac_cv_exeext=.exe $ make check This fails: $ ./configure $ make EXEE