Hi,
On Sun, Jan 21, 2018 at 4:17 AM, Steffan Karger wrote:
> Hi,
>
> On 21-01-18 06:37, Selva Nair wrote:
>>
>> On Sat, Jan 20, 2018 at 11:41 AM, Steffan Karger wrote:
>>>
>>> This by default enables the compiler warnings any could previously
>>> enable using the --enable-strict configure option
Hi,
On 21-01-18 06:37, Selva Nair wrote:
>
> On Sat, Jan 20, 2018 at 11:41 AM, Steffan Karger wrote:
>>
>> This by default enables the compiler warnings any could previously
>> enable using the --enable-strict configure option. I think it is
>> okay to do so now, because we've taken care of man
Hi,
On Sat, Jan 20, 2018 at 11:41 AM, Steffan Karger wrote:
>
> This by default enables the compiler warnings any could previously
> enable using the --enable-strict configure option. I think it is
> okay to do so now, because we've taken care of many warnings in the
> more standard builds. (Mo
This by default enables the compiler warnings any could previously
enable using the --enable-strict configure option. I think it is
okay to do so now, because we've taken care of many warnings in the
more standard builds. (Most of those were totally harmless, but they
prevented us from spotting n
