Bug#811579: FTBFS with GCC 6: statement indented as if it were guarded by

2016-07-07 Thread Mike Gerow
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


signature.asc
Description: PGP signature


Bug#811579: FTBFS with GCC 6: statement indented as if it were guarded by

2016-01-19 Thread Martin Michlmayr
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 '/<>/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