The attached patch against current git fixes some incorrectly lower-cased
section names.
--
http://rrt.sc3d.org/ | The shorter the betterdiff --git a/doc/automake.texi b/doc/automake.texi
index c0ace40..c1df445 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -285,11 +285,11 @@
* Santiago Capel Torres wrote on Mon, Feb 25, 2008 at 12:03:27PM CET:
Weird, is there any way of declaring local macro variables?
No, unfortunately. We encourage users to use macro- or package-specific
variable prefixes, like
AC_DEFUN([SCT_FOOMACRO], [sct_var=value...])
Cheers,
Ralf
I've been looking through the manuals and code, but not finding a
definitive answer: is there a canonical/recommended ordering of running
the autotools, including automake?
I've been using aclocal - autoheader - automake - autoconf for years,
but have no idea any more where I got that ordering.
Hi Karl!
Karl Berry wrote:
I've been looking through the manuals and code, but not finding a
definitive answer: is there a canonical/recommended ordering of running
the autotools, including automake?
I really like the encapsulation offered by 'autoreconf'.
Bob
I searched for this and found no solutions, so here goes.
I'm also using autotools for a project. I'm also using bison's ability to
output C++ parsers rather than plain C parsers. When operating in this
mode, bison generates a few more files: stack.hh, location.hh, and
position.hh. The
Hi Karl,
* Karl Berry wrote on Tue, Feb 26, 2008 at 12:39:21AM CET:
I've been using aclocal - autoheader - automake - autoconf for years,
but have no idea any more where I got that ordering. I see that
autoreconf runs autoconf before autoheader, and ah before am, so I
suppose this is it:
Hello Brad,
* Brad Larsen wrote on Tue, Feb 26, 2008 at 06:11:59AM CET:
I'm also using autotools for a project. I'm also using bison's ability
to output C++ parsers rather than plain C parsers. When operating in
this mode, bison generates a few more files: stack.hh, location.hh, and
