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 = ...
(ob
> 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 958
* 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 hy
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 w
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: h
