[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: avoid new GCC-7-exposed warnings
From: |
Jim Meyering |
Subject: |
Re: avoid new GCC-7-exposed warnings |
Date: |
Sat, 15 Oct 2016 16:55:37 -0700 |
On Sat, Oct 15, 2016 at 8:56 AM, Jim Meyering <address@hidden> wrote:
> On Sat, Oct 15, 2016 at 8:40 AM, Jim Meyering <address@hidden> wrote:
>> On Sat, Oct 15, 2016 at 2:55 AM, Pádraig Brady <address@hidden> wrote:
>>> On 15/10/16 05:47, Jim Meyering wrote:
>>>> I tried to build the coreutils using very recent GCC 7, built from
>>>> latest git, and encountered a few new warnings (errors when configured
>>>> with --enable-gcc-warnings), so wrote the following to address them.
>>>> With these, everything now compiles warning free:
>>>
>>> All look good.
>
> Thanks for the review. Pushed.
That change was incomplete. Since die.h is not yet in a gnulib module,
we have to tell coreutils to distribute it, explicitly. I've just
pushed this fix:
cu-distribute-die.h.diff
Description: Text document
- avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/16
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/16
- Re: avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/16