testsuite: unset installation directory variables.

* tests/defs.in: Before test execution, be sure to unset all
installation directory variables, so they cannot have an effect
on a `make -e install' command within a test.
Report by Dagobert Michelsen.

Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>

diff --git a/ChangeLog b/ChangeLog
index c20ffbc..cac0302 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,11 @@
 2009-05-23  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
+       testsuite: unset installation directory variables.
+       * tests/defs.in: Before test execution, be sure to unset all
+       installation directory variables, so they cannot have an effect
+       on a `make -e install' command within a test.
+       Report by Dagobert Michelsen.
+
        testsuite: do not change the mode of installed Libtool files.
        * tests/defs.in: Do not use `chmod -R' on the test directory, as
        that may change or try to change the mode of installed files:

diff --git a/tests/defs.in b/tests/defs.in
index 0254d3a..d1366f1 100644 (file)
--- a/tests/defs.in
+++ b/tests/defs.in
@@ -300,9 +300,14 @@ END
 unset MFLAGS
 unset MAKEFLAGS
 unset MAKELEVEL
-unset DESTDIR
 # Unset verbosity flag.
 unset V
+# Also unset variables that will let `make -e install' divert
+# files into unwanted directories.
+unset DESTDIR
+unset prefix exec_prefix bindir datarootdir datadir docdir dvidir
+unset htmldir includedir infodir libdir libexecdir localedir mandir
+unset oldincludedir pdfdir psdir sbindir sharedstatedir sysconfdir
 # Also unset variables that control our test driver.  While not
 # conceptually independent, they cause some changed semantics we
 # need to control (and test for) in some of the tests to ensure