From: "Tom Browder" <tom.browder@gmail.com>
To: "J.C. Pizarro" <jcpiza@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: How to enable all warnings of all warnings of GCCs?
Date: Sat, 01 Dec 2007 12:38:00 -0000 [thread overview]
Message-ID: <8bc817ee0712010438o1fe43f5fw1b6b2e10742d1ad0@mail.gmail.com> (raw)
In-Reply-To: <998d0e4a0712010157h278c63cl11ec6ead6ea0eb65@mail.gmail.com>
On Dec 1, 2007 3:57 AM, J.C. Pizarro <jcpiza@gmail.com> wrote:
> -Wall doesn't enable all warnings.
>
> How to enable all warnings of all warnings of GCCs?
As far as I know, the only way to do it is add them all to the command
line. I've made a file I call Makefile.warnings which I 'include' in
my main Makefile. In it I define WARNINGS like so:
WARNINGS = -Wall
WARNINGS += -Wconversion
(etc.)
Then, in Makefile I will do something like:
g++ [options...] [sources...] $(WARNINGS)
I can individually eliminate unneeded warnings by commenting them out
in Makefile.warnings.
-Tom
Tom Browder
Niceville, Florida
USA
next prev parent reply other threads:[~2007-12-01 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 9:57 J.C. Pizarro
2007-12-01 12:38 ` Tom Browder [this message]
2007-12-01 20:46 ` John (Eljay) Love-Jensen
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=8bc817ee0712010438o1fe43f5fw1b6b2e10742d1ad0@mail.gmail.com \
--to=tom.browder@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jcpiza@gmail.com \
/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).