My libvirtd.config testing relied on automake-1.10 in that it used $(abs_top_builddir). And while that variable is defined just prior to the new use, the variable is a *shell* variable, not a make one. This fixes it to use the shell variable instead. Portability is ugly. Accommodate automake-1.9. * tests/Makefile.am (TESTS_ENVIRONMENT): Adjust PATH setting to work also with automake-1.9. Can't use $(abs_top_builddir). --- ChangeLog | 6 ++++++ tests/Makefile.am | 2 +- 2 files changed, 7 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index ea5b85b..cf1085b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2007-12-11 Jim Meyering <meyering(a)redhat.com&gt; + + Accommodate automake-1.9. + * tests/Makefile.am (TESTS_ENVIRONMENT): Adjust PATH setting + to work also with automake-1.9. Can't use $(abs_top_builddir). + Tue Dec 11 22:19:22 CET 2007 Jim Meyering <meyering(a)redhat.com&gt; Test libvirtd's config-processing code. diff --git a/tests/Makefile.am b/tests/Makefile.am index a918bcc..dfd9e34 100644 --- a/tests/Makefile.am +++ b/tests/Makefile.am @@ -65,7 +65,7 @@ endif TESTS_ENVIRONMENT = \ abs_top_builddir=`pwd`/'$(top_builddir)' \ abs_top_srcdir=`pwd`/'$(top_srcdir)' \ - PATH='$(abs_top_builddir)/qemud$(PATH_SEPARATOR)'"$$PATH" \ + PATH="$$abs_top_builddir/qemud$(PATH_SEPARATOR)$$PATH" \ $(VG) valgrind: -- 1.5.3.7.1116.gae2a9