From: Tim Prince <n8tm@aol.com>
To: gcc-help@gcc.gnu.org
Subject: Re: logging gcc messages
Date: Wed, 05 Mar 2014 17:34:00 -0000 [thread overview]
Message-ID: <53175FBD.4040408@aol.com> (raw)
In-Reply-To: <53175EDB.6060207@uni-bremen.de>
On 3/5/2014 12:28 PM, Michael Markowsky wrote:
> Dear Madam , Dear Sir
>
> I use gcc on a linux - system and wish to save the compiler messages for
> further analysation.
> so something like gcc filename.cpp>result.txt didn´t work
>
> Any idea
>
Check which shell you are running and look up how to redirect stderr to
your file; e.g. for bash et al.
gcc filename.cpp>result.txt 2>&1
--
Tim Prince
next prev parent reply other threads:[~2014-03-05 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 17:32 Michael Markowsky
2014-03-05 17:34 ` Tim Prince [this message]
2014-03-05 20:22 ` Jonathan Wakely
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=53175FBD.4040408@aol.com \
--to=n8tm@aol.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tprince@computer.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).