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

Previous Next

Full log

View this message in rfc822 format

From: selinger <at> mathstat.dal.ca (Peter Selinger)
To: 26033 <at> debbugs.gnu.org
Cc: Peter Selinger <selinger <at> mathstat.dal.ca>
Subject: bug#26033: EXEEXT not exported to tests
Date: Wed, 8 Mar 2017 15:52:49 -0400 (AST)

[Message part 1 (text/plain, inline)]

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 reproduce:
=============

Please see the attached minimal example testing2-0.0.tar.gz

The following succeeds:

$ ./configure
$ make check

The following fails (note: it is important to run "make clean" before
"./configure ac_cv_exeext=.exe", because otherwise the generated
execuable src/someprogram will not be cleaned up):

$ make clean
$ ./configure ac_cv_exeext=.exe
$ make check

The check/test-suite.log (also attached) basically says that
../src/someprogram was not found. Although the test script
check/mytest2.sh specified ../src/someprogram$EXEEXT, the EXEEXT
setting was not exported to the script.

The following succeeds:

$ ./configure ac_cv_exeext=.exe
$ make EXEEXT=.exe check

But it seems wrong that EXEEXT should have to be specified *both* at
configure and make time.

Proposed solution:
==================

The problem goes away if the maintainer inserts

"export EXEEXT"

at the beginning of check/Makefile.am. However, I believe this should
be inserted automatically by automake, because EXEEXT must normally be
available to tests.

[testing2-0.0.tar.gz (application/octet-stream, attachment)]

[test-suite.log (text/plain, attachment)]

Previous Next

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