Re: Patch to warn about non-static declaration follows static one

["Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>]

 > From: Jeffrey A Law <law@cygnus.com>
 > 
 >   > I'd like to add this flag to the gcc bootstrap procedure, however I
 >   > would prefer not to have it done for the whole bootstrap, just the gcc
 >   > top level directory.  The language subdirectories aren't supposed to
 >   > be compiled with a K&R compiler, so they don't need to be bothered
 >   > with this flag.
 >   > 
 >   > 	Is there an easy way to set this up?  (If not, I can just add
 >   > -Wtraditional to WARN_CFLAGS.)  Or, I'll just hack something up...
 > 
 > No strong opinions.  I thought WARN_CFLAGS only applied to the gcc subdir,
 > so putting it there ought to do the trick.
 > jeff

	The above about WARN_CFLAGS is true.  But what I meant was that
I want the warning to only apply to the gcc top level dir and not
gcc/java, gcc/f, gcc/ch or gcc/cp.  These directories are always
compiled with gcc so they shouldn't be forced to adhere to K&R
portability hacks, and thus can't be expected to compile with
-Wtraditional cleanly. 

	I've already got something going to do -Wtraditional only for
the gcc top level dir and will submit it shortly.  :-)

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Icon CMT Corp.