On Tue, 19 Jan 2016 16:10:20 -0800 Martin Michlmayr <t...@hpe.com> wrote:
> Package: crash
> Version: 7.1.4-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
> ...
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include 
> > -DHAVE_bfd_elf64_x86_64_vec -DHAVE_bfd_elf32_i386_vec 
> > -DHAVE_bfd_elf32_x86_64_vec -DHAVE_i386linux_vec -DHAVE_i386pei_vec 
> > -DHAVE_x86_64pei_vec -DHAVE_bfd_elf64_l1om_vec -DHAVE_bfd_elf64_k1om_vec 
> > -DHAVE_bfd_elf64_little_generic_vec -DHAVE_bfd_elf64_big_generic_vec 
> > -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec 
> > -DBINDIR=\"/usr/local/bin\" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
> > -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 
> > -fstack-protector-strong -Wformat -Werror=format-security -MT pei-i386.lo 
> > -MD -MP -MF .deps/pei-i386.Tpo -c pei-i386.c -o pei-i386.o
> > In file included from pei-i386.c:46:0:
> > coff-i386.c: In function 'coff_i386_reloc':
> > coff-i386.c:144:5: error: statement is indented as if it were guarded by... 
> > [-Werror=misleading-indentation]
> >      if (diff != 0)
> >      ^~
> > 
> > coff-i386.c:135:3: note: ...this 'if' clause, but it is not
> >    if (reloc_entry->howto->type == R_IMAGEBASE
> >    ^~
> > 
> > cc1: all warnings being treated as errors
> > Makefile:1607: recipe for target 'pei-i386.lo' failed
> > make[8]: *** [pei-i386.lo] Error 1

Hmm... I don't seem to be able to reproduce this error. Also the code
itself doesn't actually look misleading.

Maybe it was fixed in the latest 7.1.5-1 release?

-- 
Mike Gerow
ge...@mgerow.com

Attachment: signature.asc
Description: PGP signature

Reply via email to