Your message dated Fri, 01 May 2020 14:49:25 +0000
with message-id <e1juwyj-000hv0...@fasolo.debian.org>
and subject line Bug#925747: fixed in libkibi 0.1.1-2.1
has caused the Debian Bug report #925747,
regarding libkibi: ftbfs with GCC-9
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.)
--
925747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libkibi
Version: 0.1.1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9
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-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libkibi_0.1.1-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.
To build with GCC 9, either set CC=gcc-9 CXX=g++-9 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-9/porting_to.html
GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.
[...]
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking if compiler supports -pedantic... yes
checking if compiler supports -Wall... yes
checking if compiler supports -Wextra... yes
checking if compiler supports -Werror... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating doc/byteprefix.5
config.status: creating doc/Makefile
config.status: creating kibi/Makefile
config.status: creating test/Makefile
config.status: creating libkibi.pc
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
dh_auto_build -a
make -j1
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make all-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>'
Making all in doc
make[3]: Entering directory '/<<PKGBUILDDIR>>/doc'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/doc'
Making all in kibi
make[3]: Entering directory '/<<PKGBUILDDIR>>/kibi'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -pedantic -Wall
-Wextra -Werror -c -o kibi.lo kibi.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -pedantic -Wall -Wextra -Werror -c kibi.c -fPIC -DPIC
-o .libs/kibi.o
In file included from /usr/include/string.h:494,
from kibi.c:22:
In function 'strncpy',
inlined from 'get_xdg_config_home' at kibi.c:321:9,
inlined from 'get_user_config_file' at kibi.c:337:29,
inlined from 'kibi_init' at kibi.c:414:30:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error:
'__builtin_strncpy' specified bound depends on the length of the source
argument [-Werror=stringop-overflow=]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kibi.c: In function 'kibi_init':
kibi.c:315:18: note: length computed here
315 | length = strlen(xdg_config_home) + 1;
| ^~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:437: kibi.lo] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/kibi'
make[2]: *** [Makefile:482: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:370: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
--- End Message ---
--- Begin Message ---
Source: libkibi
Source-Version: 0.1.1-2.1
Done: Sudip Mukherjee <sudipm.mukher...@gmail.com>
We believe that the bug you reported is fixed in the latest version of
libkibi, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 925...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sudip Mukherjee <sudipm.mukher...@gmail.com> (supplier of updated libkibi
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 31 Mar 2020 19:34:31 +0100
Source: libkibi
Architecture: source
Version: 0.1.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung <bdr...@debian.org>
Changed-By: Sudip Mukherjee <sudipm.mukher...@gmail.com>
Closes: 925747
Changes:
libkibi (0.1.1-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix ftbfs with GCC. (Closes: #925747)
.
[ Boyuan Yang ]
* debian/control: Migrate Vcs-* fields to Salsa platform.
Checksums-Sha1:
e4e08b2d76c432dc9f4e2d44b14ae56b5ed245c5 1932 libkibi_0.1.1-2.1.dsc
296e8b9a309a36f82e525c2107780ffa5fc0b995 2780 libkibi_0.1.1-2.1.debian.tar.xz
4bb6e750f993eb8714357fbaaa12b52df032870b 6038 libkibi_0.1.1-2.1_amd64.buildinfo
Checksums-Sha256:
39505a1eae4900b02f39b6b800384cec0b04a578e2ecc0d5516cec4bff5e494e 1932
libkibi_0.1.1-2.1.dsc
d41fb223dfaee95610654351b48b3316d6008766210b6031979a6570a1612c2a 2780
libkibi_0.1.1-2.1.debian.tar.xz
1f71d1f135e236308d12d5c6212c8260893e91bf926d8df3e39f0ed701dae7c9 6038
libkibi_0.1.1-2.1_amd64.buildinfo
Files:
835ebe4c05b01ffce4e5ce91973b4a75 1932 libs optional libkibi_0.1.1-2.1.dsc
b78672978ba45d3f1d83c03078dfe521 2780 libs optional
libkibi_0.1.1-2.1.debian.tar.xz
3064faaa5ee010ae4388c74dfaba567e 6038 libs optional
libkibi_0.1.1-2.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl6sL6oACgkQwpPntGGC
Ws6kQw//dXcyYzGkx9LDpRZ8kFVf/oOF8lk7FGFJl2Ul5grSN9HJ++khOY/YjEIt
QtZosUGyedmUmIMsmLtlJlSo0SAbP6aB1mQDuplNJ8YhaDjB/XnreGLEo/LxV053
gFVXBqiw0JClcC+jPHRQn/fNtRizwKKsmOLdbTV3m1B+BzXruG6nESJDoB1rwcgP
Zx1uVHu980njwwSCJROCl23lFUn6taKe17DR42Sjio7KQUOAdkeLci8JiN6SP6vH
TJAlX9R+OAL/oM8MkxPaatjpRxZeMKWgU/vNqepv+az1mCPQ9W2cARDO6Q0LNHrX
z/CqtvU62HX4sxK+hkNdeEuD27+98SD3zwkP3cMsWbnWFlHqZNBqVT+IAadE6hdP
4A3dJOf1F8Aymv7HwInMzIl6BEHTiT/Cg01Oso9wn/y+jHqM900qpVnl8jAkMHSv
H6T2eqgBpLpRA2JTv+scylNv+thp6KmDEqo0WSYvP/qdo03poR5jLP5KB7hxFxO2
cPvOmowN//APIsSgVeUsMIguXBDxPd23GPl8goWTiLeRfUPOYRiyZOQZ27j9dEmn
QNfOHyuYP7p2OR1m9IfMkSUSBQeXYe9L6uhBgp94C5gK0+yhrFMWmKUXf+d9mQkU
I3zcOUVRCPEP6E16oS/bg+QAICJivL0J8UyX7jnNQGcqz1UvZzc=
=4jdu
-----END PGP SIGNATURE-----
--- End Message ---
