Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

To: 848917@bugs.debian.org, Adrian Bunk <bunk@stusta.de>, Andreas Beckmann <anbe@debian.org>
Subject: Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
From: Graham Inggs <ginggs@debian.org>
Date: Fri, 13 Jan 2017 13:47:18 +0200
Message-id: <[🔎] 76b1da34-747c-7749-00eb-1196da4eb543@debian.org>
Reply-to: Graham Inggs <ginggs@debian.org>, 848917@bugs.debian.org
In-reply-to: <[🔎] 76852aa8-d6d3-c581-4832-48631a44a78d@debian.org>
References: <[🔎] 76852aa8-d6d3-c581-4832-48631a44a78d@debian.org>

Thanks for the upload, Andreas!

If this bug had been tagged [1] like #811740 was, I might have seen itsooner.

I only saw it when I noticed nautic was not migrating in Ubuntu. :(

[1]https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-6;users=debian-gcc@lists.debian.org

Reply to:

Follow-Ups:
- Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
  - From: Andreas Beckmann <anbe@debian.org>

References:
- Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
  - From: Graham Inggs <ginggs@debian.org>