Hi Eric,
* Eric Blake wrote on Tue, Dec 04, 2007 at 06:36:44PM CET:
I was annoyed that a with fresh git checkout, 'autoreconf -fi' downgraded
texinfo.tex;
So don't use --force.
I traced it to the fact that I was not using bleeding-edge
automake. This fixes it, so I'm committing.
Well,
* Makefile.am, doc/install.texi, lib/autoconf/fortran.m4,
lib/autoconf/lang.m4, lib/freeze.mk: Likewise.
---
These files all had changes this year. I have applied this patch.
Cheers,
Ralf
Makefile.am |2 +-
doc/install.texi|2 +-
lib/autoconf/fortran.m4 |2 +-
Hello,
I've applied this to master.
Cheers,
Ralf
* doc/autoconf.texi (autom4te Invocation, Autom4te Cache): Fix typos.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index d6bd786..3d76b3e 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -9906,7 +9906,7 @@ traces are cached
Hello autoconf-patches,
Here's a series of patches that, when applied, should allow for mostly
arbitrary characters
- in the absolute name of the source and build trees of Autoconf
(but not in the relative $srcdir -- of course `make' cannot cope with
that),
- in $TMPDIR,
- in the name of the
This includes escaping of characters special to the shell
as well as special to Perl, e.g., leading `' or `'.
For example, when $file starts with `', `open $file'
wrongly tries to append to a different file.
* bin/autoconf.as: Fix quoting for autom4te options.
* lib/Autom4te/General.pm
Eric Blake [EMAIL PROTECTED] writes:
But it does raise the question - does autoconf's configure.ac really work
with
automake as old as 1.7.9, or should we up our minimum requirement to 1.9.6 or
1.10? It also raises a documentation bug against Automake - the manual
mentions
---
This patch is not actually needed for the build to succeed in a
build tree name containing whitespace. However, it prevents
`distcheck' to fail very early. In fact, at the end of the patch
series, `distcheck' only fails very late, in `installcheck'.
Cheers,
Ralf
lib/autom4te.in | 10
The problem here is that the usual mantra is that command
variables can contain arguments, thus we cannot just escape
$AUTOCONF, $AUTOM4TE etc. The compromise is to put the
$top_builddir/tests directory early in $PATH, so that the
wrappers are found by their plain name.
* tests/wrapper.as: Put
Ralf Wildenhues [EMAIL PROTECTED] writes:
This includes escaping of characters special to the shell as well as
special to Perl, e.g., leading `' or `'. For example, when $file
starts with `', `open $file' wrongly tries to append to a different
file.
The best fix here from a Perl perspective
* tests/local.at (AT_CHECK_PERL_SYNTAX): Likewise.
* tests/tools.at (Syntax of the shell scripts): Likewise.
---
tests/local.at |2 +-
tests/tools.at | 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/tests/local.at b/tests/local.at
index b17fff3..75823e2 100644
---
tests/semantics.at |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/tests/semantics.at b/tests/semantics.at
index f2c59f3..9e3da84 100644
--- a/tests/semantics.at
+++ b/tests/semantics.at
@@ -554,6 +554,11 @@ AT_CLEANUP
AT_SETUP([AC_PATH_PROGS_FEATURE_CHECK])
* tests/autotest.at (srcdir propagation): Copy install-sh to
source tree.
(my only test): Drop setting of `top_srcdir'.
* tests/base.at (Input/Output): Likewise.
* tests/local.at (AT_CONFIGURE_AC): Copy install-sh,
config.guess, and config.sub to test source tree.
Drop AC_CONFIG_AUX_DIR setting.
---
This test actually calls configure with an absolute path,
so in a tree with whitespace we need to quote (just like
most of the code under autoconf/lib does, too).
Cheers,
Ralf
tests/torture.at |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/torture.at
Ralf Wildenhues [EMAIL PROTECTED] writes:
but I wouldn't know how to make it foolproof. First, if the space is
missing after `' and $file begins with `', then append mode is used.
But also, if $file begins with whitespace, that is just ignored anyway.
I'm a bit out of context here, but can't
Ralf Wildenhues [EMAIL PROTECTED] writes:
+# $FILE_NAME
+# shell_quote ($FILE_NAME)
+#
+# If the string $S is a well-behaved file name, simply return it.
+# If it contains white space, quotes, etc., quote it, and return
+# the new string.
+sub shell_quote($)
+{
+
Ralf Wildenhues [EMAIL PROTECTED] writes:
-case `sed -n '/datarootdir/ {
+case `eval cat $ac_file_inputs | sed -n '/datarootdir/ {
...
-])' $ac_file_inputs` in
+])'` in
I'd rather not turn one subprocess into two just to overcome some
shell quoting issue. How about doing it this way
Ralf Wildenhues [EMAIL PROTECTED] writes:
We should at least be given the chance to
release either in the state licenses are done now, or with GPL2 (given
consent of recent contributors).
I don't know the details about Automake, but for Autoconf I see no
problem with releasing unger GPLv3
Just a feature request for autoreconf: the ability to get the equivalent
of aclocal -I dirname with ACLOCAL_AMFLAGS is fine if you're using
automake, but not all projects do. (I'm using Bakefile, for instance,
because I also need to generate Visual C++ project files and such.)
It'd be great
Hello Brett,
Are there news on the license exception rewording for Autoconf,
Automake, and Libtool?
There were previous discussions of this topic here:
http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/4658/focus=2854
and you sent an update to gnu-prog on Aug 27, stating that it
19 matches
Mail list logo
