Message-ID: <3AE6EC0C.CC4E487D@falconsoft.be>
Date: Wed, 25 Apr 2001 17:23:56 +0200
From: Tim Van Holder <tim DOT vanholder AT falconsoft DOT be>
Organization: Falcon Software NV
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-3 i686)
X-Accept-Language: en, nl-BE, nl
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Seeing errors from gcc in DOS
References: <3ae6dc8f DOT 13867961 AT news DOT earthlink DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 24
NNTP-Posting-Host: 194.78.64.238
X-Trace: 988212222 reader1.news.skynet.be 20625 194.78.64.238
X-Complaints-To: abuse AT skynet DOT be
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

dan AT no DOT spam wrote:
> 
> Hi,
> 
> I've tried redirecting output to a file. ( gcc -c -Wall cname.c > e.txt ). It
> creates e.txt, but it's blank.
> 
> I've tried redirecting stderr ( 3>e.txt ). Ditto.
Hmmm. stderr is fd 2, so that should have been 2>e.txt; or even better
(assuming
you're using bash): gcc ... 2>&1 >e.txt (this gets both normal output
and errors).

Under command.com, you could also use DJGPP's redir program to redirect
standard
output and/or standard error.  It's what it's there for (in the olden
days there
was no bash for DJGPP).

-- 
Tim Van Holder - Falcon Software N.V.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message was posted using plain text. I do not endorse any
products or services that may be hyperlinked to this message.