[bind10-dev] Use of -Werror in release tarballs

[Mark Andrews]

In message <20130220074538.GA20637 at totoro>, Mukund Sivaraman writes:
> Hi all
> 
> This is a request for feedback on whether we should include or remove
> -Werror from the release tarballs.
> 
> The -Werror compiler flag causes compiler warnings to become errors, and
> aborts the compile. In the BIND 10 master tree, this flag is enabled by
> default when performing compiles. Should we use this flag by default in
> the release tarball too?
> 
> The effect of adding this flag is that in case a future version of a
> compiler notices anything that it should warn about (that may or may not
> be a problem) when compiling the stable BIND 10 release, it will abort
> the compile.
> 
> We have some arguments for and against including this flag. Without
> mentioning them here, this is a request polling everyone (esp. those who
> intend to compile BIND 10 from source) to give their input. It will
> affect whether we ship BIND 10 stable releases with the flag included or
> not.
> 
> 		Mukund

It turns a perfectly good tarball into a broken tarball whenever
compiler developers decide to catch minor issues.

It's something that developers should be able turn on when developing
but should be off for releases.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org