Message-ID: <001501be70ed$bd862dc0$078a7ad1@hlb.cable.rcn.com>
From: "Roger Beeman" <topos AT erols DOT com>
To: <djgpp AT delorie DOT com>
Subject: Re: gcc reported bad command
Date: Wed, 17 Mar 1999 22:16:31 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Reply-To: djgpp AT delorie DOT com

Eli--
Thanks for the quick response.  I ran your suggested language, the path
slightly modified, thusly,

 G:\DJGPP\bin>redir -o gcc.log -eo gcc -v hello.c -o hello.exe

 The generated  file 'gcc.log'  reads
"Bad command or file name" and that's it.

Any other ideas would be greatly appreciated.

----- Original Message -----
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups: comp.os.msdos.djgpp
To: Roger Beeman <topos AT erols DOT com>
Cc: <djgpp AT delorie DOT com>
Sent: Wednesday, March 17, 1999 9:20 AM
Subject: Re: gcc reported bad command


>
>On Wed, 17 Mar 1999, Roger Beeman wrote:
>
>> Type at DOS in the box (Win95OSR2.5) prompt:
>>
>> G:\DJGPP\bin gcc hello.c -o hello.exe   [enter]
>> Bad command or file name
>
>Type this instead:
>
>  G:\DJGPP\bin\redir -o gcc.log -eo gcc -v hello.c -o hello.exe [enter]
>
>This will create a file called `gcc.log'.  Look at that file, it might
>give a hint about what goes wrong.  If you cannot figure it out, post
the
>entire contents of that file here, and somebody will spot the problem.