From:	"DeHackEd" <not DOT given AT out>
Newsgroups:	comp.os.msdos.djgpp
References:	<3783B188 DOT 570A5AE6 AT eudoramail DOT com>
Subject:	Re: Error messages with GCC
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-Mimeole:	Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID:	<MGRg3.1358$Pd2.5800@cabot.ops.attcanada.net>
Date:	Wed, 07 Jul 1999 23:47:56 GMT
NNTP-Posting-Host:	142.194.222.186
X-Trace:	cabot.ops.attcanada.net 931391276 142.194.222.186 (Wed, 07 Jul 1999 23:47:56 GMT)
NNTP-Posting-Date:	Wed, 07 Jul 1999 23:47:56 GMT
Lines:	18
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Is there a command-line argument for sending GCC error messages to a
> file rather than the standard error stream?  If not, is there any other
> way to save the messages to a file?
>
> Thanks

There isn't a command line, but there is a program that will redirect stderr
to stdout, vice versa, or to files. It's called "redir". Just run
"redir --help" at the dos prompt to see the syntax, but the basic syntax is:

redir -e stderr_file.txt gcc myfile.c ...

--
DeHackEd

No emails, the address is fake.

- Raw text -