public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Piping Compiler Output
@ 2002-08-31 19:08 Scott Barnett
  2002-08-31 21:33 ` Phil Edwards
  0 siblings, 1 reply; 2+ messages in thread
From: Scott Barnett @ 2002-08-31 19:08 UTC (permalink / raw)
  To: gcc

Hello,

I'd like to write the output of the gcc compiler to a file (logging). I've
tried using the > operator, but that doesn't seem to work, and I also
download the source to cat, and modified it so it logged to file instead of
printing text, and that won't work either (although it does work if I do an
ls or any other simple command).

Any ideas?

Regards, Scott.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Piping Compiler Output
  2002-08-31 19:08 Piping Compiler Output Scott Barnett
@ 2002-08-31 21:33 ` Phil Edwards
  0 siblings, 0 replies; 2+ messages in thread
From: Phil Edwards @ 2002-08-31 21:33 UTC (permalink / raw)
  To: Scott Barnett; +Cc: gcc

On Sun, Sep 01, 2002 at 12:06:26PM +1000, Scott Barnett wrote:
> Hello,
> 
> I'd like to write the output of the gcc compiler to a file (logging). I've
> tried using the > operator, but that doesn't seem to work,

The compiler also writes to standard error.  How to redirect that depends on
your shell.  Try

    gcc ..... > file 2>&1


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-08-31 21:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-08-31 19:08 Piping Compiler Output Scott Barnett
2002-08-31 21:33 ` Phil Edwards

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).