On Wed, Aug 01, 2001 at 07:40:38PM +0200, Akim Demaille wrote:
>
> I've just uploaded Autoconf 2.52b (for Autoconf 2.52a was broken, of
> course...).
[...]
> Basically you can consider 2.52b is nothing but 2.52 atop autom4te.
> But it requires extensive testing (aka, ``use it at your own risks'' :).
> I've been using it for a while, and seems to behaves properly.
> Please, as usual, torture it.
I just tested autoconf 2.52b under Tru64 v5.1 and found the same
problem previoulsy reported with CVS :
autom4te command line generation in autoconf use `"$@"' instead of
`${1+"$@"}'. Under Tru64, this generate empty parameters that
autom4te doesn't like.
Here follow a small patch.
--
Nicolas Joly
Informatique Scientifique
Institut Pasteur, Paris.
Index: ChangeLog
===================================================================
RCS file: /cvs/autoconf/ChangeLog,v
retrieving revision 1.1530
diff -u -r1.1530 ChangeLog
--- ChangeLog 2001/08/01 21:21:23 1.1530
+++ ChangeLog 2001/08/02 08:47:27
@@ -1,3 +1,8 @@
+2001-08-02 Nicolas Joly <[EMAIL PROTECTED]>
+
+ * bin/autoconf.in: Use `${1+"$@"}' not `"$@"' to avoid empty
+ argument in autom4te command line under Tru64.
+
2001-08-01 Akim Demaille <[EMAIL PROTECTED]>
* configure.ac: Bump to 2.52c.
Index: bin/autoconf.in
===================================================================
RCS file: /cvs/autoconf/bin/autoconf.in,v
retrieving revision 1.132
diff -u -r1.132 autoconf.in
--- bin/autoconf.in 2001/08/01 13:58:44 1.132
+++ bin/autoconf.in 2001/08/02 08:47:42
@@ -232,8 +232,8 @@
# Autom4te expansion.
eval set dummy "$traces"
shift
-$verbose "$me: running $run_autom4te ""$@"" $infile --output $outfile" >&2
-$run_autom4te "$@" $infile --output $outfile ||
+$verbose "$me: running $run_autom4te "${1+"$@"}" $infile --output $outfile" >&2
+$run_autom4te ${1+"$@"} $infile --output $outfile ||
{ (exit 1); exit 1; }
if test -z "$traces" && test "x$outfile" != x-; then
