Applied to master.

FWIW, I'm kind of wondering whether to even post patches FYI here that
are already applied -- since the git repo will post them, at least for
trivial ones like this one and the other one I just applied, there isn't
much added value.

Of course, if people don't like that mode of operation, then I should
let the autogenerated ones go to another mailing list.

Comments?

Cheers,
Ralf

    Quote @abs_top_builddir@ and @[EMAIL PROTECTED]
    
    * tests/aclocal.in: Likewise.
    * tests/automake.in: Likewise.

diff --git a/tests/aclocal.in b/tests/aclocal.in
index ea3464c..35b1619 100644
--- a/tests/aclocal.in
+++ b/tests/aclocal.in
@@ -14,5 +14,5 @@ perllibdir="@abs_top_builddir@/[EMAIL 
PROTECTED]@@abs_top_srcdir@/lib"
 export perllibdir
 # Most of the files are in $srcdir/../m4.  However amversion.m4 is
 # generated in ../m4, so we include that directory in the search path too.
-exec @abs_top_builddir@/aclocal $ACLOCAL_TESTSUITE_FLAGS \
-     -I @abs_top_builddir@/m4 [EMAIL PROTECTED]@/m4 ${1+"$@"}
+exec "@abs_top_builddir@/aclocal" $ACLOCAL_TESTSUITE_FLAGS \
+     -I "@abs_top_builddir@/m4" "[EMAIL PROTECTED]@/m4" ${1+"$@"}
diff --git a/tests/automake.in b/tests/automake.in
index 4a86345..d4c4c5c 100644
--- a/tests/automake.in
+++ b/tests/automake.in
@@ -12,4 +12,4 @@ fi
 
 perllibdir="@abs_top_builddir@/[EMAIL PROTECTED]@@abs_top_srcdir@/lib"
 export perllibdir
-exec @abs_top_builddir@/automake [EMAIL PROTECTED]@/lib ${1+"$@"}
+exec "@abs_top_builddir@/automake" "[EMAIL PROTECTED]@/lib" ${1+"$@"}


Reply via email to