Hi Ralf!
Ralf Wildenhues ralf.wildenh...@gmx.de writes:
* Ralf Wildenhues wrote on Sat, Jul 31, 2010 at 02:11:59PM CEST:
* Ludovic Courtès wrote on Tue, Jul 27, 2010 at 11:08:39AM CEST:
FYI the Automake test suite currently fails on Hydra. The build at
http://hydra.nixos.org/build/502179
Hi Ralf!
Ralf Wildenhues ralf.wildenh...@gmx.de writes:
* Ralf Wildenhues wrote on Sat, Jul 31, 2010 at 02:11:59PM CEST:
* Ludovic Courtès wrote on Tue, Jul 27, 2010 at 11:08:39AM CEST:
FYI the Automake test suite currently fails on Hydra. The build at
http://hydra.nixos.org/build/502179
Hello,
I know that pattern rules are not portable. When we use one pattern rule, then
we call autoreconf, we can see this warning :
man/Makefile.am:8: `%'-style pattern rules are a GNU make extension
So if we want a protable project, we should not use them in a Makefile.am file.
But we can use
In a Makefile, the relative order of variable and rule
definitions matters, because variables used in targets are
expanded when rules are read. If a variable is used in a target
before the variable is changed, the variable's former expansion
is used in the target, not the latter expansion.
Hi Ben,
* Ben Pfaff wrote on Wed, Aug 25, 2010 at 07:22:58PM CEST:
Current Automake appears to reorder the Makefile.am so that all
variable assignments precede all rules, so in a Makefile.am the
relative order of variable and rule definitions does not matter.
Right.
Is this behavior
Hello,
* YuGiOhJCJ Mailing-List wrote on Wed, Aug 25, 2010 at 11:14:15AM CEST:
I know that pattern rules are not portable. When we use one pattern
rule, then we call autoreconf, we can see this warning :
man/Makefile.am:8: `%'-style pattern rules are a GNU make extension
So if we want a
