* [gentoo-dev] inherit nowarn
@ 2002-06-07 2:27 Spider
2002-06-07 9:14 ` Paul de Vrieze
0 siblings, 1 reply; 2+ messages in thread
From: Spider @ 2002-06-07 2:27 UTC (permalink / raw
To: gentoo-dev
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [gentoo-dev] inherit nowarn
2002-06-07 2:27 [gentoo-dev] inherit nowarn Spider
@ 2002-06-07 9:14 ` Paul de Vrieze
0 siblings, 0 replies; 2+ messages in thread
From: Paul de Vrieze @ 2002-06-07 9:14 UTC (permalink / raw
To: gentoo-dev
On Friday 07 June 2002 04:27, Spider wrote:
>
> 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?
I like the second, if you mean to say that pedantic, Wall, etc will be deleted
from the build flags. Not using warnings is in normal cases a good thing (not
when it goes wrong). Maybe an option to put warnings on (not remove them) in
ebuild would be apropriate for debugging.
Paul
--
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-06-07 9:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-07 2:27 [gentoo-dev] inherit nowarn Spider
2002-06-07 9:14 ` Paul de Vrieze
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox