Hello Oleg,
* Oleg V. Zhylin wrote on Tue, Nov 27, 2007 at 12:52:52AM CET:
This time I'm running Automake 1.10. According to 6.3.4 Handling
Local Macros in the manual
ACLOCAL_AMFLAGS = -I m4
line should instruct both autoreconf and make to use these flags when
autoconf is executed.
Just to be sure: you put the ACLOCAL_AMFLAGS line in the toplevel
Makefile.am file? The file is named exactly Makefile.am? There is
no whitespace before the word `ACLOCAL_AMFLAGS'?
Yes to all three. One further detail. As I debugged my package automake
eventually captured ACLOCAL_AMFLAGS
Hello,
On Tue, Nov 27, 2007 at 12:30:31AM +, Olly Betts wrote:
Handling Tools that Produce Many Outputs. However, these recipes
require a lot of boilerplate code which annoyingly obscures [...]
It's just struck me that automake is good at inserting lots of
boilerplate code into
On 2007-11-27, Stepan Kasal [EMAIL PROTECTED] wrote:
On Tue, Nov 27, 2007 at 12:30:31AM +, Olly Betts wrote:
data.c data.h::: data.foo
foo data.foo
But this looks like too much magic for a feature which is not used
that much.
My experience is that multi-output rules
On Nov 27, 2007 9:54 AM, Olly Betts [EMAIL PROTECTED] wrote:
In fact, none of the real examples I have to hand fit into the mould of
a collection of implicit rules with a common basename.
Cheers,
Olly
Just to toss a couple more pennies into the pot, I am currently working
on a poject
On Tue, 27 Nov 2007, Olly Betts wrote:
My experience is that multi-output rules often aren't protected at all,
and parallel make is unreliable on such projects. This is becoming much
more of an issue, as multicore boxes are now mainstream.
What relationship is there between parallel make and
On 2007-11-27, Bob Friesenhahn [EMAIL PROTECTED] wrote:
On Tue, 27 Nov 2007, Olly Betts wrote:
My experience is that multi-output rules often aren't protected at all,
and parallel make is unreliable on such projects. This is becoming much
more of an issue, as multicore boxes are now
