Jim Meyering wrote:
...
> Yes, it looks like if we're using both of those, we'll have to
> add code to reject -Wuninitialized (maybe with a warning?) when
> configuring without -O.
...
> [here's simple PoC, i.e., it doesn't know about -O0,
> but you get the idea ]
>
> W = -Wuninitialized -Werror
>
Eric Blake wrote:
> On 09/06/2012 06:48 AM, Jim Meyering wrote:
>>
>> Actually, with GNU make, this is something that we could probably
>> adjust at make-time.
>
> Only if you use Automake-NG, and can assume GNU make.
IMHO, this work-around doesn't have to do anything for those using
non-GNU make,
On 09/06/2012 06:48 AM, Jim Meyering wrote:
>
> Actually, with GNU make, this is something that we could probably
> adjust at make-time.
Only if you use Automake-NG, and can assume GNU make.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
Eric Blake wrote:
> On 09/06/2012 12:07 AM, Jim Meyering wrote:
>> Eric Blake wrote:
>>
>>> I compiled on FreeBSD 8.2 (gcc 4.2.1), and when I updated to the latest
>>> gnulib, I started to see the following in config.log when running
>>> ./configure CFLAGS=-g:
>>>
>
>> When you configure with one
On 09/06/2012 12:07 AM, Jim Meyering wrote:
> Eric Blake wrote:
>
>> I compiled on FreeBSD 8.2 (gcc 4.2.1), and when I updated to the latest
>> gnulib, I started to see the following in config.log when running
>> ./configure CFLAGS=-g:
>>
> When you configure with one set of warning options and l
Eric Blake wrote:
> I compiled on FreeBSD 8.2 (gcc 4.2.1), and when I updated to the latest
> gnulib, I started to see the following in config.log when running
> ./configure CFLAGS=-g:
>
> configure:53920: checking whether C compiler handles -Wuninitialized
> configure:53939: gcc -std=gnu99 -c -g
