Re: sections without nodes in automake manual?

Hi Karl, thanks for the quick review! * Karl Berry wrote on Fri, Mar 27, 2009 at 11:26:24PM CET: +* SUBDIRS vs DIST_SUBDIRS:: Two sets of directories Probably a period after vs, to match the @subsection name (and because this manual is (primarily?) in American English rather than

Re: sections without nodes in automake manual?

* Unfortunately, you cannot use periods, commas, colons or parentheses within a node name; these confuse the Texinfo processors. Perhaps this limitation will be removed some day, too. Oh yeah :). Well, the situation is that in practice, periods only cause trouble in

Re: sections without nodes in automake manual?

Hi Karl, * Karl Berry wrote on Sat, Mar 28, 2009 at 11:25:26PM CET: * Unfortunately, you cannot use periods, commas, colons or parentheses within a node name; these confuse the Texinfo processors. Perhaps this limitation will be removed some day, too. Oh yeah :).

manual: minor cleanups.

This trivial patch fixes a couple of minor glitches in the manual. Committed to master and branch-1-10. Cheers, Ralf manual: minor cleanups. * doc/automake.texi (Yacc and Lex): Adjust spacing in example. (Mixing Fortran 77 With C and C++): Drop unneeded @page breaks. diff --git

Re: proposed patch: parallel-tests: per-extension test driver: ext_COMPILE.

* Ralf Wildenhues wrote on Tue, Mar 24, 2009 at 10:57:16PM CET: How about this? I really appreciate a look over this. Note that for extension .foo, the variable names will be FOO_LOG_*, i.e., remove the dot, then uppercase the rest. I chose to go all the way and add AM_*FLAGS too. One

check-html: Always create HTML output, note conversion failure.

* Akim Demaille wrote on Sat, Mar 14, 2009 at 01:39:07PM CET: # Be sure to run check-TESTS first, and then to convert the result. # Beware of concurrent executions. Run check, not check-TESTS, # since the dependencies (check_PROGRAMS and others) are attached to # the former, not the latter.

parallel-tests: do not mark check-TESTS as `.MAKE'.

This patch fixes a small glitch I overlooked earlier. Pushed to ad-parallel-tests. Cheers, Ralf parallel-tests: do not mark check-TESTS as `.MAKE'. * lib/am/check.am [PARALLEL_TESTS] (.MAKE): Remove check-TESTS. This rule removes files, which should not be executed with BSD

parallel-tests: redo lazy checking: recheck and RECHECK_LOGS.

Hi Akim, * Akim Demaille wrote on Sat, Mar 14, 2009 at 01:39:07PM CET: For the records, here is the version I use currently, some of bugs you mentioned being fixed. I don't know which was the last I sent, so I can't send a patch. Among changes that I believe, are worth mentioning are:

[PATCH] build: use automake's --silent-rules option when possible

I like automake's upcoming --silent-rules option enough that I'm making it the default (when possible) for coreutils. Since I bootstrap using automake from its next branch, it's enabled for me. And that translates to enhanced Makefile.in files in the tarballs I generate. The net result is that

Re: [PATCH] build: use automake's --silent-rules option when possible

On Sat, 28 Mar 2009, Jim Meyering wrote: I like automake's upcoming --silent-rules option enough that I'm making it the default (when possible) for coreutils. Since I bootstrap using automake from its next branch, it's enabled for me. And that translates to enhanced Makefile.in files in the

Re: [PATCH] build: use automake's --silent-rules option when possible

Ralf Corsepius rc040...@freenet.de writes: Jim Meyering wrote: Since I bootstrap using automake from its next branch, it's enabled for me. And that translates to enhanced Makefile.in files in the tarballs I generate. The net result is that when you run make (using distributed Makefile.in