[PATCH:xorg-docs] Release Notes: add note about new strict compilation flags

[Jeremy Huddleston]

Please make a note that if their build fails with the default CFLAGS, they should file a bug about it.

Sent from my iPhone...

On Mar 30, 2012, at 20:45, Alan Coopersmith <alan.coopersmith at oracle.com> wrote:

> Signed-off-by: Alan Coopersmith <alan.coopersmith at oracle.com>
> ---
> general/ReleaseNotes.xml |   21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
> 
> diff --git a/general/ReleaseNotes.xml b/general/ReleaseNotes.xml
> index a02a75e..75ed70b 100644
> --- a/general/ReleaseNotes.xml
> +++ b/general/ReleaseNotes.xml
> @@ -946,6 +946,27 @@ url="http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-2012-0064.html"
>   <sect1 id='Build_changes_and_issues'>
>     <title>Build changes and issues</title>
> 
> +    <sect2 id='Strict_compilation_flags'>
> +      <title>Strict compilation flags</title>
> +
> +      <para>
> +        Most of the modules in this release use stricter compiler flags,
> +        when used with the GNU gcc, LLVM clang, Oracle Solaris Studio, or
> +        Intel compilers.   These flags both enable more warnings, and
> +        promote some warnings to fatal errors in the build.   If these
> +        flags cause your build to fail, you can disable the flags that
> +        turn these selected warnings into errors by adding
> +        <option>--disable-selective-werror</option> to the configure command
> +        for the affected module.
> +      </para>
> +
> +      <para>
> +        Builders seeking even stricter compiler checks can instead pass
> +        <option>--enable-strict-compilation</option> to the configure command
> +        to make all warnings become errors.
> +      </para>
> +    </sect2>
> +
>     <sect2 id='Silent_build_rules'>
>       <title>Silent build rules</title>
> 
> -- 
> 1.7.9.2
>