From: br engineering <br_engineering@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: GCC output console cannot be pipe thru more
Date: Wed, 15 Oct 2003 06:24:00 -0000 [thread overview]
Message-ID: <20031015062405.67916.qmail@web12001.mail.yahoo.com> (raw)
GCC Help
I am using GCC for the first time to recompile a
driver for an enet card on RH9. GCC outputs so many
warnings and errors that the terminal buffer is
overfilled in Gnome desktop. I can see the top message
in a bash shell only but cannot store to a file. I
tried "gcc .... > outfile" but only got the invocation
line. Please comment I have refer to the gcc manual
with no luck except to get the preprocessor messages
only by halting compilation.
br
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
next reply other threads:[~2003-10-15 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 6:24 br engineering [this message]
2003-10-15 6:33 ` m.
2003-10-15 16:47 lrtaylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031015062405.67916.qmail@web12001.mail.yahoo.com \
--to=br_engineering@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).