[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#853519: marked as done (linux: ftbfs with GCC-7)

Your message dated Tue, 20 Jun 2017 16:42:13 +0100
with message-id <1497973333.27368.36.camel@decadent.org.uk>
and subject line Re: linux: ftbfs with GCC-7
has caused the Debian Bug report #853519,
regarding linux: ftbfs with GCC-7
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 owner@bugs.debian.org
immediately.)


-- 
853519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853519
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 4.9.2-2
Severity: normal
Tags: sid buster
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/linux_4.9.2-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[8]: Leaving directory '/<<PKGBUILDDIR>>/tools/perf'
/<<PKGBUILDDIR>>/tools/build/Makefile.build:134: recipe for target 'util' failed
make[7]: *** [util] Error 2
make[7]: *** Waiting for unfinished jobs....
make[7]: Leaving directory '/<<PKGBUILDDIR>>/tools/perf'
Makefile.perf:365: recipe for target '/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/perf-in.o' failed
make[6]: *** [/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/perf-in.o] Error 2
make[6]: *** Waiting for unfinished jobs....
   ld  -r -o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/libperf-in.o  /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/annotate.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/hists.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/map.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/scripts.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/header.o
make[9]: Leaving directory '/<<PKGBUILDDIR>>/tools/perf'
   ld  -r -o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/libperf-in.o  /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/setup.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/helpline.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/progress.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/util.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/hist.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/stdio/hist.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browser.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/browsers/libperf-in.o /<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/ui/tui/libperf-in.o
make[8]: Leaving directory '/<<PKGBUILDDIR>>/tools/perf'
make[7]: Leaving directory '/<<PKGBUILDDIR>>/tools/perf'
Makefile.perf:559: recipe for target '/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/libperf-in.o' failed
make[6]: *** [/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/libperf-in.o] Error 2
/<<PKGBUILDDIR>>/tools/perf/util/thread_map.c: In function 'thread_map__new_by_uid':
/<<PKGBUILDDIR>>/tools/perf/util/thread_map.c:119:39: error: '%s' directive output may be truncated writing between 0 and 255 bytes into a region of size 250 [-Werror=format-truncation=]
   snprintf(path, sizeof(path), "/proc/%s", dirent->d_name);
                                       ^~
In file included from /usr/include/stdio.h:938:0,
                 from /<<PKGBUILDDIR>>/tools/perf/util/thread_map.c:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 7 and 262 bytes into a destination of size 256
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        __bos (__s), __fmt, __va_arg_pack ());
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
error: command 'gcc' failed with exit status 1
cp: cannot stat '/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/python_ext_build/lib/perf.so': No such file or directory
Makefile.perf:264: recipe for target '/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/python/perf.so' failed
make[6]: *** [/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf/python/perf.so] Error 1
make[6]: Leaving directory '/<<PKGBUILDDIR>>/tools/perf'
/<<PKGBUILDDIR>>/debian/rules.d/tools/perf/Makefile:59: recipe for target 'all' failed
make[5]: *** [all] Error 2
make[5]: Leaving directory '/<<PKGBUILDDIR>>/debian/build/build-tools/tools/perf'
/<<PKGBUILDDIR>>/debian/rules.d/Makefile.inc:25: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/debian/build/build-tools/tools'
/<<PKGBUILDDIR>>/debian/rules.d/Makefile.inc:25: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/debian/build/build-tools'
debian/rules.real:534: recipe for target 'debian/stamps/build-tools' failed
make[2]: *** [debian/stamps/build-tools] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules.gen:396: recipe for target 'build-arch_amd64_real' failed
make[1]: *** [build-arch_amd64_real] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:41: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

--- End Message ---
--- Begin Message --- 
Version: 4.11-1~exp1

These errors appear to have all been fixed upstream in 4.11-rc1.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
                               A fail-safe circuit will destroy others.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: