Your message dated Sat, 5 Aug 2017 09:34:08 +0200
with message-id <20170805073408.d2zuqn2nqpa4npgo@eldamar.local>
and subject line Re: Bug#853359: criu: ftbfs with GCC-7
has caused the Debian Bug report #853359,
regarding criu: 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 ow...@bugs.debian.org
immediately.)


-- 
853359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:criu
Version: 2.9-2
Severity: normal
Tags: sid buster
User: debian-...@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/criu_2.9-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

[...]
  CC       criu/sysctl.o
criu/log.c: In function 'print_on_level':
criu/log.c:58:11: error: '%06u' directive output may be truncated writing 
between 6 and 10 bytes into a region of size 8 [-Werror=format-truncation=]
    "(%02u.%06u)", (unsigned)t.tv_sec, (unsigned)t.tv_usec);
           ^~~~
criu/log.c:58:4: note: using the range [0, 4294967295] for directive argument
    "(%02u.%06u)", (unsigned)t.tv_sec, (unsigned)t.tv_usec);
    ^~~~~~~~~~~~~
criu/log.c:57:2: note: format output between 12 and 24 bytes into a destination 
of size 12
  snprintf(buffer, TS_BUF_OFF,
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
    "(%02u.%06u)", (unsigned)t.tv_sec, (unsigned)t.tv_usec);
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CC       criu/timerfd.o
  CC       criu/sysfs_parse.o
  CC       criu/tun.o
  CC       criu/tty.o
  CC       criu/util.o
  CC       criu/uts_ns.o
  CC       criu/vdso.o
cc1: all warnings being treated as errors
/<<PKGBUILDDIR>>/scripts/nmk/scripts/build.mk:103: recipe for target 
'criu/log.o' failed
make[3]: *** [criu/log.o] Error 1
make[3]: *** Waiting for unfinished jobs....
criu/tty.c: In function 'pty_alloc_fake_reg':
criu/tty.c:499:53: error: '%u' directive output may be truncated writing 
between 1 and 10 bytes into a region of size 6 [-Werror=format-truncation=]
     snprintf(&inverted_path[slash_at + 1], 10, "pts/%u",
                                                     ^~
criu/tty.c:499:48: note: using the range [1, 4294967295] for directive argument
     snprintf(&inverted_path[slash_at + 1], 10, "pts/%u",
                                                ^~~~~~~~
criu/tty.c:499:5: note: format output between 6 and 15 bytes into a destination 
of size 10
     snprintf(&inverted_path[slash_at + 1], 10, "pts/%u",
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       info->tie->pty->index);
       ~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
/<<PKGBUILDDIR>>/scripts/nmk/scripts/build.mk:103: recipe for target 
'criu/tty.o' failed
make[3]: *** [criu/tty.o] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
criu/Makefile:82: recipe for target 'criu/built-in.o' failed
make[2]: *** [criu/built-in.o] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
Makefile:214: recipe for target 'criu' failed
make[1]: *** [criu] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

--- End Message ---
--- Begin Message ---
Hi

I cannot reproduce the failure anymore even with 2.9-2. Looking from
the failure I guess this was the upstream compiler bug as reported at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 .

Regards,
Salvatore

--- End Message ---

Reply via email to