X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
Date: Thu, 7 Mar 2002 07:59:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: deckerben <deckerben AT freenet DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: Postal posting brings success.
In-Reply-To: <3c867327$0$140$9b622d9e@news.freenet.de>
Message-ID: <Pine.SUN.3.91.1020307075623.8027E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 6 Mar 2002, deckerben wrote:

> Why would the make no error-out when the bash called
> 'D:\USER\DJGPP\BIN\GCC.EXE' (as it usually did before I changed the
> environment.

Because Make itself _does_ support backslashes in many contexts.  
Disabling that support would mean many DOS and Windows makefiles will not 
be able to run with the DJGPP port of GNU Make.

The trouble begins when the backslashed line gets to Bash, especially if 
the Bash commands in the makefile were not written to carefully quote its 
arguments.

> But make would only be unable to find GCC when the path was
> 'D:\\USER\\DJGPP\\BIN\\GCC.EXE'.

I'm guessing that it was Bash who couldn't find GCC unless you use two 
backslashes in a row.  Make itself should have no trouble.