X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: "deckerben" <deckerben AT freenet DOT de>
Newsgroups: comp.os.msdos.djgpp
References: <3c84dfb6$0$4080$9b622d9e AT news DOT freenet DOT de> <3c84f79a DOT sandmann AT clio DOT rice DOT edu> <3c84fe5f$0$12305$9b622d9e AT news DOT freenet DOT de> <3c860c12$0$4076$9b622d9e AT news DOT freenet DOT de> <a654h0$7sh$1 AT antares DOT lu DOT erisoft DOT se> <3c86314e$0$159$9b622d9e AT news DOT freenet DOT de> <9743-Wed06Mar2002205416+0200-eliz AT is DOT elta DOT co DOT il>
Subject: Re: Postal posting brings success.
Date: Wed, 6 Mar 2002 21:05:06 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Lines: 31
Message-ID: <3c867327$0$140$9b622d9e@news.freenet.de>
NNTP-Posting-Host: 213.6.188.100
X-Trace: 1015444264 news.freenet.de 140 213.6.188.100
X-Complaints-To: abuse AT freenet DOT de
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Thank you.

    Yes that makes sense, as bash is Unix and needs a Unix slash. OK. Now my
question:

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. Those ARE backslashes, too, right?
But make would only be unable to find GCC when the path was
'D:\\USER\\DJGPP\\BIN\\GCC.EXE'. THAT always hosed it up.
And now I know what causes it.



"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> wrote in message
news:9743-Wed06Mar2002205416+0200-eliz AT is DOT elta DOT co DOT il...
> > From: "deckerben" <deckerben AT freenet DOT de>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Wed, 6 Mar 2002 16:23:19 +0100
> >
> > The real problem was THIS:
> > You remember that the makefile was always trying to execute
> > D:\\USER\\DJGPP\\BIN\\GCC.EXE
> > This was caused by a SYSTEM VARIABLE that I had set up:
> >     SET CC=D:\USER\DJGPP\BIN\GCC.EXE
>
> Those backslashes triggered my questions about misconfigured
> installation.  Bash (and any scripts it runs) should never see
> backslashes.