Provide end users with a workaround if they find code doesn't build with
the -Werror=... flags provided by BASE_CFLAGS. This can be useful if
newer util-macros are used with older source code that had problems, or
in the rare case when warnings are expanded to hit more cases (although
this case sh
On 11-12-20 09:13 PM, Alan Coopersmith wrote:
On 12/19/11 18:50, Jeremy Huddleston wrote:
Provide end users with a workaround if they find code doesn't build with
the -Werror=... flags provided by BASE_CFLAGS. This can be useful if
newer util-macros are used with older source code that had prob
On 12/19/11 18:50, Jeremy Huddleston wrote:
Provide end users with a workaround if they find code doesn't build with
the -Werror=... flags provided by BASE_CFLAGS. This can be useful if
newer util-macros are used with older source code that had problems, or
in the rare case when warnings are exp
Sent from my iPhone...
On Dec 20, 2011, at 5:58, Gaetan Nadon wrote:
> On Mon, 2011-12-19 at 18:50 -0800, Jeremy Huddleston wrote:
>>
>> Provide end users with a workaround if they find code doesn't build with
>> the -Werror=... flags provided by BASE_CFLAGS. This can be useful if
>> newer u
On Mon, 2011-12-19 at 18:50 -0800, Jeremy Huddleston wrote:
> Provide end users with a workaround if they find code doesn't build with
> the -Werror=... flags provided by BASE_CFLAGS. This can be useful if
> newer util-macros are used with older source code that had problems, or
> in the rare cas
Provide end users with a workaround if they find code doesn't build with
the -Werror=... flags provided by BASE_CFLAGS. This can be useful if
newer util-macros are used with older source code that had problems, or
in the rare case when warnings are expanded to hit more cases (although
this case sh
