public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joel Dice <dicej@mailsnare.net>
To: Andrew Bell <andrew.bell.ia@gmail.com>
Cc: kamelopardus <killorn@yandex.ru>, gcc-help@gcc.gnu.org
Subject: Re: gcc warnings
Date: Tue, 12 Aug 2008 15:52:00 -0000	[thread overview]
Message-ID: <alpine.DEB.0.999.0808120947410.30073@joeldicepc.ecovate.com> (raw)
In-Reply-To: <e80abd30808120835p5448b473wee46c8d5d4a98b09@mail.gmail.com>

On Tue, 12 Aug 2008, Andrew Bell wrote:

> On Tue, Aug 12, 2008 at 10:25 AM, kamelopardus <killorn@yandex.ru> wrote:
>>
>> Hello.
>>
>> I use gcc 3.4.2 under mingw32. I need to put compiler warnings about
>> uninitialized variables into some text file, for example, "warnings.txt".
>>
>> i try
>>
>> gcc -O -Wuninitialized -v echo.c>warnings.txt
>
> They are going to stderr, not stdout.  Try:
>
> gcc -O -Wuninitialized -v echo.c 2>& > warnings.txt

I think you mean:

gcc -O -Wuninitialized -v echo.c > warnings.txt 2>&1

  reply	other threads:[~2008-08-12 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 15:36 kamelopardus
2008-08-12 15:48 ` Andrew Bell
2008-08-12 15:52   ` Joel Dice [this message]
2008-08-12 17:19   ` kamelopardus
  -- strict thread matches above, loose matches on Subject: below --
2007-10-17  9:08 Humpolicek, Jiri - Acision
2007-10-17 11:48 ` John Love-Jensen
2007-10-17 11:49 ` Tom St Denis
2007-10-17 14:08   ` Humpolicek, Jiri - Acision
2007-10-17 13:28 ` Tim Prince
2007-10-17 14:28   ` Humpolicek, Jiri - Acision
2007-10-17 15:25     ` Andrew Haley
2000-05-24 14:29 Zia Babar
2000-05-24 23:48 ` Martin v. Loewis

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=alpine.DEB.0.999.0808120947410.30073@joeldicepc.ecovate.com \
    --to=dicej@mailsnare.net \
    --cc=andrew.bell.ia@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=killorn@yandex.ru \
    /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).