At 10:52 AM 1/28/2003 -0800, gk wrote:
>Mystery solved: make evalutes substring after the command-line '=' in the
MAKEFILE context, NOT in the shell.
This explains the loss of leading white space and the 'double evaluation'.
Well, actually it still isn't solved: if make was simply evaluating what
the shell handed it in the makefile context, then FOO should INCLUDE the
leading backslash.
What is make doing with the backslash?
It seems to be trying to do a makefile evaluation but is allowing the
backslash as an escape character, rather than a literal, as it always does
inside a makefile.
That really is inconsistent.
- Greg Keraunen
http://www.xmake.org
http://www.xmlmake.com
_______________________________________________
Help-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-make
