Date: Tue, 23 Feb 1999 17:40:06 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bug in make?
In-Reply-To: <m10FIxH-000S6hC@inti.gov.ar>
Message-ID: <Pine.SUN.3.91.990223173303.9620B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Tue, 23 Feb 1999, Salvador Eduardo Tropea (SET) wrote:

> Then make should process argv[0]. After all that's the normal case when 
> called from command line and not spawned.

I would prefer to solve a local problem (i.e. backslashes mishandling in 
Makefile command lines) locally.  This means that the function which 
interprets the command lines read from a Makefile should be changed to 
not strip the backslashes under some conditions, so that cases like what 
you reported would work.

OTOH, what you suggest has a global effect (it changes how the value of
$(MAKE) will look in recursive Make's) which could break something,
somewhere.  Who knows, maybe some Makefile out there writes the value of 
$(MAKE) to a file and expects it to be with backslashes?