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.
Trying to test the behaviour of $(EXEEXT) on platforms where it's normally empty is, IMHO, futile. This isn't an autoconf test whose result one should ever override.
Although the test script check/mytest2.sh specified ../src/someprogram$EXEEXT, the EXEEXT setting was not exported to the script.
You don't need $(EXEEXT) to run the executable --- only to check the file, which tests won't have to do.
