Re: [PATCH] {master} Extend and improve tests on DejaGnu support.

Ping on this? Reference: http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00143.html I will wait the customary 72 hours (until friday evening) before pushing. Regards, Stefano

Re: [PATCH] Improve and extend tests `pluseq*.test' (on `+=' support).

Ping on this? Reference: http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00087.html In the meantime, I've amended the patch a bit; in particular, I've rebased it on the latest maint branch, I've removed some useless (I mean *really* useless) make distcheck calls, and I've relaxed

Re: [PATCH 0/5] More patches for the tests-init branch

Hello automakers. In reference to this thread: http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00186.html On Monday 15 November 2010, Stefano Lattarini wrote: Stefano Lattarini (5): Tests defs: avoid some useless subshells. Tests required tools: also try `-v' option for GNU

Re: Fwd: [Bug 347095] installing m4 macros that break random packages

Hi Eric, Thank you. automake list folks -- the main question is Why are .m4 files being installed and how can I prevent it? Original Message Subject: [Bug 347095] sys-devel/autogen installs colliding \ m4 macros which break random packages Clear-Text:

Re: recursive make variables coming to POSIX

On 12/07/10 01:54, Schwarz, Konrad wrote: as well as listing in the rationale examples such as $($(@)_FLAGS) and $(V$O) that are unspecified. $($...@_flags) is a very useful, as it allows target-specific flags. For all targets whose name conforms to make macro name requirements. It would

Re: recursive make variables coming to POSIX

* Bruce Korb wrote on Tue, Dec 07, 2010 at 08:36:16PM CET: On 12/07/10 01:54, Schwarz, Konrad wrote: $($...@_flags) is a very useful, as it allows target-specific flags. For all targets whose name conforms to make macro name requirements. Right. But since period is allowed, only hyphen

RE: recursive make variables coming to POSIX

Meanwhile, this may work as an appropriate wording that still permits IRIX behavior, by stating that recursive expansion is only specified for parenthesized variables that are not one of the five internal macros (@, %, ?, , *), and only when nested with () or {}: Change line 95800:

Re: Fwd: [Bug 347095] installing m4 macros that break random packages

On Tuesday, December 07, 2010 13:56:35 Bruce Korb wrote: Thank you. automake list folks -- the main question is Why are .m4 files being installed and how can I prevent it? because your top level Makefile.am is using: aclocal_DATA = ... when i think you should be using: noinst_DATA = ...