Your message dated Wed, 20 Jan 2016 00:42:28 +0000 with message-id <[email protected]> has caused the report #811581, regarding FTBFS with GCC 6: statement indented as if it were guarded by to be marked as having been forwarded to the upstream software author(s) [email protected]
(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 [email protected] immediately.) -- 811581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811581 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---On Tue, Jan 19, 2016 at 03:59:48PM -0800, Martin Michlmayr wrote: > 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 > ... > > gcc -DHAVE_CONFIG_H -I. -I././ -I./charset/ -I./windows/ -I./unix/ > > -I./macosx/ -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -pthread > > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > > -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 > > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > > -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 > > -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 > > -Wall -Werror -g -O2 -fPIE -fstack-protector-strong -Wformat > > -Werror=format-security -c -o sshrand.o sshrand.c > > proxy.c: In function 'proxy_socks5_negotiate': > > proxy.c:1191:31: error: statement is indented as if it were guarded by... > > [-Werror=misleading-indentation] > > if (ulen > 255) ulen = 255; if (ulen < 1) ulen = 1; > > ^~ > > > > proxy.c:1191:3: note: ...this 'if' clause, but it is not > > if (ulen > 255) ulen = 255; if (ulen < 1) ulen = 1; > > ^~ > > > > proxy.c:1193:31: error: statement is indented as if it were guarded by... > > [-Werror=misleading-indentation] > > if (plen > 255) plen = 255; if (plen < 1) plen = 1; > > ^~ > > > > proxy.c:1193:3: note: ...this 'if' clause, but it is not > > if (plen > 255) plen = 255; if (plen < 1) plen = 1; > > ^~ > > > > cproxy.c: In function 'proxy_socks5_selectchap': > > cproxy.c:176:30: error: statement is indented as if it were guarded by... > > [-Werror=misleading-indentation] > > if (ulen > 255) ulen = 255; if (ulen < 1) ulen = 1; > > ^~ > > > > cproxy.c:176:2: note: ...this 'if' clause, but it is not > > if (ulen > 255) ulen = 255; if (ulen < 1) ulen = 1; > > ^~ Hi putty@, This is perhaps a bit of an annoying warning in this particular case, although I can see why GCC thought it would be a good idea in general. Would you prefer to try to detect whether -Wno-error=misleading-indentation is available and use it, or restructure the code (which I suppose is just a matter of newlines before the second "if" in each case) to accommodate it? https://gcc.gnu.org/gcc-6/changes.html documents this change. Thanks, -- Colin Watson [[email protected]]
--- End Message ---
