bug#26033: EXEEXT not exported to tests

2017-06-17 Thread Mathieu Lirzin
severity 26033 wishlist tag 26033 wontfix close 26033 thanks Hello Peter, selin...@mathstat.dal.ca (Peter Selinger) writes: > =?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

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 platforms where EXEEXT is non-empty,

bug#26033: EXEEXT not exported to tests

2017-03-09 Thread Hans-Bernhard Bröker
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 platforms where EXEEXT is non-empty, scripts do _not_ need to know about it to start executables, i.e.

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