On Tue, May 18, 2010 at 02:42:31PM -0400, Alfred M. Szmidt wrote: > That doesn't explain why though, which is what I'm interested in. The > `if' construct is automakeism and gets expanded during ./configure, > whilst ifdef is makeism and is dynamic.
Yes, that's why -- automake only knows about "if", not "ifdef", so if it sees an "endif" without a corresponding "if" it'll assume you forgot one. There's no provision for passing through GNU-make-specific stuff like ifdef, which is probably a good thing since it means you can't use it by accident in a Makefile that you intended to be portable... -- Adam Sampson <a...@offog.org> <http://offog.org/>
