GNU bug report logs - #26033
EXEEXT not exported to tests

Previous Next

Package: automake;

Reported by: selinger <at> mathstat.dal.ca (Peter Selinger)

Date: Wed, 8 Mar 2017 19:54:01 UTC

Severity: wishlist

Tags: wontfix

Done: Mathieu Lirzin <mthl <at> gnu.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Hans-Bernhard Bröker <HBBroeker <at> t-online.de>
To: Peter Selinger <selinger <at> mathstat.dal.ca>, 26033 <at> debbugs.gnu.org
Subject: bug#26033: EXEEXT not exported to tests
Date: Thu, 9 Mar 2017 21:46:16 +0100

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.
This bug report was last modified 7 years and 336 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.