Re: Bigger picture of automake variables

2008-12-21 Thread Ralf Wildenhues
* LCID Fire wrote on Sun, Dec 21, 2008 at 07:40:00PM CET: > Ralf Wildenhues wrote: > > >> So basically variables are not ever transported between Makefiles. > > Correct. > Is this written down somewhere on the docs? Not really. > > Well, what really happens is that, with > > AC_SUBST([VARIABLE

Re: Bigger picture of automake variables

2008-12-21 Thread LCID Fire
Ralf Wildenhues wrote: > [ moving from automake@ ] > > Hello, > > * LCID Fire wrote on Sun, Dec 14, 2008 at 07:51:07PM CET: >> Ralf Wildenhues wrote: >>> Elsewhere, flags like AM_LDFLAGS are denoted as global. In that case, >>> it is meant to say that, unlike program_LDFLAGS, which applies to >>

Re: Bigger picture of automake variables

2008-12-21 Thread Ralf Wildenhues
[ moving from automake@ ] Hello, * LCID Fire wrote on Sun, Dec 14, 2008 at 07:51:07PM CET: > Ralf Wildenhues wrote: > > Elsewhere, flags like AM_LDFLAGS are denoted as global. In that case, > > it is meant to say that, unlike program_LDFLAGS, which applies to > > 'program' only, the flags apply

Re: AM_OUTPUT_DEPENDENCY_COMMANDS problem

2008-12-21 Thread Ralf Wildenhues
Hello Markus, Eric, * Duft Markus wrote on Fri, Dec 19, 2008 at 11:48:37AM CET: > > I found a problem with AM_OUTPUT_DEPENDENCY_COMMANDS. I disabled > dependency tracking through the configure command line option, and with > recent automake (1.10.2) I kept getting errors like this: > [...] > con