Re: more compile warnings with new factor

[Eric Blake]

On 10/23/2012 03:44 AM, Jim Meyering wrote:

> This is a good reason to enable that consistently.  Eric, since the
> log (modulo small edits) and patch are yours, you're the author, so I'll
> wait for your ACK before pushing these to their respective repositories.

Sure - go for it in all of these projects.

> In order, those are:
> 
>   grep
>   diffutils
>   idutils
>   cppi
>   parted
> 
> The logs are identical, as are the patches, modulo offsets.
> 
>>From 85eaa86258bbdc17894355a1720dc9efda9044ed Mon Sep 17 00:00:00 2001
> From: Eric Blake <address@hidden>
> Date: Tue, 23 Oct 2012 11:30:29 +0200
> Subject: [PATCH] build: default to --enable-gcc-warnings in a git tree
> 
> Anyone building from cloned sources can be assumed to have a new
> enough environment, such that enabling gcc warnings by default will
> be useful.  Tarballs still default to no warnings, and the default
> can still be overridden with --disable-gcc-warnings.
> * configure.ac (gl_gcc_warnings): Set default based on environment.

-- 
Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature