public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] inherit nowarn
Date: Fri, 7 Jun 2002 04:27:27 +0200	[thread overview]
Message-ID: <20020607042727.04978bd7.spider@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

well, this is a little RFC...

Since (according to the gcc FAQ, and "common sense" ) the flags -Wall
and other extra warnings, pedantic and so on would requires more
time/output to work, I'm suggesting a simple(?) eclass to recursively
parse a source tree, match all "Makefile" and "makefile" and strip out
extra warning flags from them.

Why? Simple speed/convenience in many cases.
Example, mozilla currently does a loooot of bad warnings due to gcc 3.1
incompabilities (deprecated headers)

that sort of thing could be fixed with a "inherit nowarn" and
"strip_warnings()" 

quoting gcc faq:

  Note  that  using -pedantic or -Wreturn-type can cause an explosion in
   the  amount of memory needed for template-heavy C++ code, such as
code
   that  uses STL. Also note that -Wall includes -Wreturn-type, so if
you
   use -Wall you will need to specify -Wno-return-type to turn it off.

one way would be to add "-Wnoall" (not sure aobut this) and others would
be to simply match "pedantic" "Wall" "Wdeprecated" and add a
"Wno-deprecated" to kill all warnings.

ideas on this approach please?

//Spider



--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2002-06-07  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07  2:27 Spider [this message]
2002-06-07  9:14 ` [gentoo-dev] inherit nowarn Paul de Vrieze

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=20020607042727.04978bd7.spider@gentoo.org \
    --to=spider@gentoo.org \
    --cc=gentoo-dev@gentoo.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