Your message dated Thu, 7 Jul 2016 11:15:02 -0400
with message-id 
<CAMzhQmNphMNbXCFRMpsCqKcuggu=rbxjwn-jug0op1509e2...@mail.gmail.com>
and subject line Re: Bug#811579: FTBFS with GCC 6: statement indented as if it 
were guarded by
has caused the Debian Bug report #811579,
regarding FTBFS with GCC 6: statement indented as if it were guarded by
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
811579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mosh
Version: 1.2.5-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /usr/bin/protoc --cpp_out=. -I. transportinstruction.proto
> make  all-am
> make[5]: Entering directory '/<<PKGBUILDDIR>>/src/protobufs'
> g++ -DHAVE_CONFIG_H -I. -I../..  -pthread  -Wall -Werror -fno-strict-overflow 
> -D_FORTIFY_SOURCE=2 -fstack-protector-all -Wstack-protector --param 
> ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g -O2 -c -o userinput.pb.o 
> userinput.pb.cc
> userinput.pb.cc: In member function 'virtual bool 
> ClientBuffers::Instruction::IsInitialized() const':
> userinput.pb.cc:375:53: error: statement is indented as if it were guarded 
> by... [-Werror=misleading-indentation]
>    if (!_extensions_.IsInitialized()) return false;  return true;
>                                                      ^~~~~~
> 
> userinput.pb.cc:375:3: note: ...this 'if' clause, but it is not
>    if (!_extensions_.IsInitialized()) return false;  return true;
>    ^~
> 
> cc1plus: all warnings being treated as errors

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

--- End Message ---
--- Begin Message ---
Package: mosh
Version: 1.2.5.95rc1-1

Fixed by ec6980da960910ddacc676575fe3d4743b8f7c59

On Thu, Jul 7, 2016 at 10:52 AM, Mike Gerow <ge...@mgerow.com> wrote:

> The code in question is generated by the protobuf compiler. Since humans
> shouldn't be reading this code anyway I think it's safe to disable the
> warning here. Looking to see if there's a good way to selectively
> disable it just for the proto bits...
>
> --
> Mike Gerow
> ge...@mgerow.com
>

--- End Message ---

Reply via email to