On Tue, Jul 09, 2013 at 03:20:01PM +0100, Michael Tautschnig wrote: > Hello Kurt, > > I have just run into related problems with the new automake version, but also > did some more digging: > > It seems TESTS_ENVIRONMENT *is* used/available, it's just now part of the > definition of am__check_pre. But if you happen to use it to specify a wrapper > (like I did), this won't work anymore, as is detailed here: > > http://www.gnu.org/software/automake/manual/automake.html#Parallel-Test-Harness > > I don't know what the symptoms were that you observed (which led to the > diagnosis of TESTS_ENVIRONMENT having been lost), but maybe this helps.
It's set to a shell script that set up environment variables like LD_LIBRARY_PATH. Looking at the manual in 15.2.1: | The AM_TESTS_ENVIRONMENT and TESTS_ENVIRONMENT variables can be | used to run initialization code and set environment variables for | the test scripts. [...] | AM_TESTS_ENVIRONMENT = \ | ## Some environment initializations are kept in a separate shell | ## file 'tests-env.sh', which can make it easier to also run tests | ## from the command line. | . $(srcdir)/tests-env.sh; \ Then in 15.2.3 it says: | the AM_TESTS_ENVIRONMENT and TESTS_ENVIRONMENT variables _cannot_ be use | to define a custom test runner; the LOG_COMPILER and LOG_FLAGS | (or their extension-specific counterparts) should be used instead: | | ## This is WRONG! | AM_TESTS_ENVIRONMENT = PERL5LIB='$(srcdir)/lib' $(PERL) -Mstrict -w | | ## Do this instead. | AM_TESTS_ENVIRONMENT = PERL5LIB='$(srcdir)/lib'; export PERL5LIB; | LOG_COMPILER = $(PERL) | AM_LOG_FLAGS = -Mstrict -w So the manual is contradicting itself. And if it's not supported anymore, it's breaking an documented way of doing things. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
