Appartements sans vis-à-vis avec une vue imprenable à Casablanca Finance City!
Afin de voir votre message, cliquez sur le lien: http://link.news-sarouty.ma/v/443/de86ac2aa9610f17b45f7afe4c9f778393b2665fc349b5b3
Bug#983902: marked as done (sendmail: reproducible builds: embeds build path in site.config.m4 documentation files)
Your message dated Wed, 03 Mar 2021 11:50:13 +
with message-id
and subject line Bug#983902: fixed in sendmail 8.15.2-21
has caused the Debian Bug report #983902,
regarding sendmail: reproducible builds: embeds build path in site.config.m4
documentation files
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.)
--
983902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendmail
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The build path is embedded in the site.config.m4 files shipped in the
documentation of sendmail-doc and sendmail-base packages:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/sendmail.html
/usr/share/doc/sendmail-base/site.config.m4.gz
define(`confOPTIMIZE',··`-g·-O2·-ffile-prefix-map=/build/1st/sendmail-8.15.2=.·-fstack-pro..
vs.
define(`confOPTIMIZE',··`-g·-O2·-ffile-prefix-map=/build/2/sendmail-8.15.2/2nd=.·-fstack-pro...
The attached patch fixes this by replacing the build path with
"BUILDPATH" in debian/rules before installing the documentation.
With this patch applied, sendmail should become reproducible.
Thanks for maintaining sendmail!
live well,
vagrant
From 3d28d581a7b6de3be07e13b75b093f535bb71a41 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Wed, 3 Mar 2021 02:17:36 +
Subject: [PATCH] debian/rules: Avoid embedding the build path in
site.config.m4.
The site.config.m4 file is shipped in sendmail-doc and sendmail-base,
but should have the build path removed in the shipped file.
https://tests.reproducible-builds.org/debian/issues/unstable/records_build_flags_issue.html
---
debian/rules | 2 ++
1 file changed, 2 insertions(+)
diff --git a/debian/rules b/debian/rules
index 0c4fe82..f7b2405 100755
--- a/debian/rules
+++ b/debian/rules
@@ -203,6 +203,8 @@ override_dh_auto_install-arch:
#
override_dh_installdocs-indep:
+ # Avoid recording the build path in the documentation
+ sed -i -e "s,prefix-map=$(CURDIR),prefix-map=BUILDPATH,g" debian/build/site.config.m4
dh_installdocs -p${DEB_SOURCE_PACKAGE}-doc --doc-main-package=${DEB_SOURCE_PACKAGE}-doc -A $(DEB_SRCDIR)/README
dh_installdocs -N${DEB_SOURCE_PACKAGE}-doc -A $(DEB_SRCDIR)/README
--
2.30.1
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sendmail
Source-Version: 8.15.2-21
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
sendmail, 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 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated sendmail 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: SHA256
Format: 1.8
Date: Wed, 03 Mar 2021 12:03:42 +0100
Source: sendmail
Architecture: source
Version: 8.15.2-21
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 983902
Changes:
sendmail (8.15.2-21) unstable; urgency=medium
.
* QA upload.
* Make the build reproducible, thanks to Vagrant Cascadian.
(Closes: #983902)
* Move amavis documentation to /usr/share/doc/sendmail.
* Bump watch version to 4. No changes needed.
* Update to Standards-Version: 4.5.1.
* Fix more typos found by Lintian.
* Update Lintian overrides.
Checksums-Sha1:
463a6339e123201d8ed2b749a5a1ba39ab5444ba 2801 sendmail_8.15.2-21.dsc
ef51db9653169646f3f7bde67ab30408b40f53a9 227392
sendmail_8.15.2-21.debian.tar.xz
4fac3c3e020a71d11baa4a8acf00bdeb2c885f14 6127
sendmail_8.15.2-21_source.buildinfo
Checksums-Sha256:
0298a6ca54ba8808e028c6523272c7d9543072d90ff827b266254265df40be12 2801
sendmail_8.15.2-21.dsc
1456533eda0d396acb7df380d2b07260b0cabb8bcd912a28b467ca4353d9d4d0 227392
sendmail_8.15.2-21.debian.tar.xz
3cdd77637ea89b430d4a0265fd608ab9d3c8b49a38f886974ba1c345ded437df 6127
sendmail_8.15.2-21_source.buildinfo
Files:
21a665db50bef4a3946ec1edd
Processing of sendmail_8.15.2-21_source.changes
sendmail_8.15.2-21_source.changes uploaded successfully to localhost along with the files: sendmail_8.15.2-21.dsc sendmail_8.15.2-21.debian.tar.xz sendmail_8.15.2-21_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#983902: sendmail: reproducible builds: embeds build path in site.config.m4 documentation files
Fix uploaded, please take care of an unblock if you think this should be in bullseye. Andreas
sendmail_8.15.2-21_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Mar 2021 12:03:42 +0100 Source: sendmail Architecture: source Version: 8.15.2-21 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 983902 Changes: sendmail (8.15.2-21) unstable; urgency=medium . * QA upload. * Make the build reproducible, thanks to Vagrant Cascadian. (Closes: #983902) * Move amavis documentation to /usr/share/doc/sendmail. * Bump watch version to 4. No changes needed. * Update to Standards-Version: 4.5.1. * Fix more typos found by Lintian. * Update Lintian overrides. Checksums-Sha1: 463a6339e123201d8ed2b749a5a1ba39ab5444ba 2801 sendmail_8.15.2-21.dsc ef51db9653169646f3f7bde67ab30408b40f53a9 227392 sendmail_8.15.2-21.debian.tar.xz 4fac3c3e020a71d11baa4a8acf00bdeb2c885f14 6127 sendmail_8.15.2-21_source.buildinfo Checksums-Sha256: 0298a6ca54ba8808e028c6523272c7d9543072d90ff827b266254265df40be12 2801 sendmail_8.15.2-21.dsc 1456533eda0d396acb7df380d2b07260b0cabb8bcd912a28b467ca4353d9d4d0 227392 sendmail_8.15.2-21.debian.tar.xz 3cdd77637ea89b430d4a0265fd608ab9d3c8b49a38f886974ba1c345ded437df 6127 sendmail_8.15.2-21_source.buildinfo Files: 21a665db50bef4a3946ec1edd7508dbc 2801 mail optional sendmail_8.15.2-21.dsc 4f85d5e0e5e05b1d6208e994e9e08957 227392 mail optional sendmail_8.15.2-21.debian.tar.xz ad112fade058b3419eda57859bbf1ba8 6127 mail optional sendmail_8.15.2-21_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmA/c64QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCFmLD/9c4xXl6lM3T6hjAcu2+Yh5klEOlLSTZ8Xn RPNm4iVcuLbkkVFV/+qisB5GmDkD8yU9jAza5NVYaHdQFk/WpLlfRP2lCUtJlzqs SuSjZuRZsaTHURqdkXwwQTuxpREvL0LJ2InYcVKeq4B7lhJLWarZQsUTCNhIXIEi qKJgRTZFASvEWYzAVazq0B3Y+zbsuGut28BRVP7GSNYGqvVu4fYR+AMpDMgZp921 avc6GHi3b3tEaDFsmjFKRvwI0sKnzRmLNNeGlogskDILusQ4Ctp4q7T47Ynnt+Ev X5fIhgwLqtdE8GxugLlT62R6DaHnFQs+WRJ22pCOg9CYMqL2qMMjN/pdlu1dK++w 4UNKnWwej5JiNhifYZn/fKoduS/3sYhqNGfZNz1F1B0hDO1ajhvDgJTZnRtTaSpE cT2xGcyK//QHZdoQO94Fxv9MNfHOv8LJTw7YI3V50a/DHII0pCl+YXEqvYxcKP9B hCRupgcr5O85j6aEHOfpbNNMTCwosKjQ2yO7hsB1ZwmH7giRNbYSOzdRXfeUXRqy QbyneM5cyck5Shkq9V6cwv8Oyt/0P71phUBNIlEgaSfTsejmcc/xf7PzsCw3rXay cysI4sU6iKmEkAx98ilDv/xbWeGo94hImXjInvhSwRELFwMUVavTNoY7av7dpNn5 5hQl6t/fHw== =EGTg -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#984002: boxbackup: ftbfs with GCC-11
Package: src:boxbackup Version: 0.13~~git20200326.g8e8b63c-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/boxbackup_0.13~~git20200326.g8e8b63c-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] lib/win32 lib/common lib/raidfile lib/crypto lib/server lib/compress lib/intercept test/common test/crypto test/compress test/raidfile test/basicserver lib/backupstore lib/backupclient lib/bbackupd lib/bbackupquery lib/bbstored bin/bbackupobjdump bin/bbstored bin/bbstoreaccounts bin/bbackupd bin/bbackupquery bin/bbackupctl test/backupstore test/backupstorefix test/backupstorepatch test/backupdiff test/bbackupd bin/s3simulator test/s3store lib/httpserver test/httpserver Type 'cd ; make' to build a module A summary of the build configuration is below. Box Backup will function without these features, but will work better where they are present. Refer to the documentation for more information on each feature. Regular expressions: yes Large files: yes Berkeley DB: yes Readline:yes Extended attributes: yes Debugger:neither GDB nor LLDB detected! touch configure-stamp dh_testdir /usr/bin/make V=1 make[1]: Entering directory '/<>' g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/bbackupd -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"bin/bbackupd\"" -c bin/bbackupd/bbackupd.cpp -o release/bin/bbackupd/bbackupd.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"lib/bbackupd\"" -c lib/bbackupd/BackupClientContext.cpp -o release/lib/bbackupd/BackupClientContext.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"lib/bbackupd\"" -c lib/bbackupd/BackupClientDeleteList.cpp -o release/lib/bbackupd/BackupClientDeleteList.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"lib/bbackupd\"" -c lib/bbackupd/BackupClientDirectoryRecord.cpp -o release/lib/bbackupd/BackupClientDirectoryRecord.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"lib/bbackupd\"" -c lib/bbackupd/BackupClientInodeToIDMap.cpp -o release/lib/bbackupd/BackupClientInodeToIDMap.o g++ -g -Wall -Werror=return-type -Werror
Bug#984007: ccbuild: ftbfs with GCC-11
Package: src:ccbuild Version: 2.0.7+git20160227.c1179286-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/ccbuild_2.0.7+git20160227.c1179286-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] In file included from /<>/src/MD5Info/MD5Info.ih:21, from /<>/src/MD5Info/save.cc:18: /<>/src/MD5Info/../fileSystem/fileSystem.hh:138:56: error: ISO C++17 does not allow dynamic exception specifications 138 | static time_t modTime(std::string const &file) throw (Problem); |^ In file included from /<>/src/MD5Info/MD5Info.ih:21, from /<>/src/MD5Info/statics.cc:19: /<>/src/MD5Info/../fileSystem/fileSystem.hh:138:56: error: ISO C++17 does not allow dynamic exception specifications 138 | static time_t modTime(std::string const &file) throw (Problem); |^ In file included from /<>/src/ccbuild.cc:21: /<>/src/system/system.hh:204:90: error: ISO C++17 does not allow dynamic exception specifications 204 | static int system(std::string const &command, bool simulate = Options::simulate) throw(Problem); | ^ /<>/src/system/system.hh:228:69: error: ISO C++17 does not allow dynamic exception specifications 228 | static std::string mkdtemp(std::string const& nameTemplate) throw(Problem); | ^ /<>/src/system/system.hh:232:39: error: ISO C++17 does not allow dynamic exception specifications 232 | static std::string username() throw(Problem); | ^ In file included from /<>/src/ccbuild.cc:23: /<>/src/fileSystem/fileSystem.hh:138:56: error: ISO C++17 does not allow dynamic exception specifications 138 | static time_t modTime(std::string const &file) throw (Problem); |^ In file included from /<>/src/MD5Info/MD5Info.ih:22, from /<>/src/MD5Info/old.cc:19: /<>/src/MD5Info/../system/system.hh:204:90: error: ISO C++17 does not allow dynamic exception specifications 204 | static int system(std::string const &command, bool simulate = Options::simulate) throw(Problem); | ^ /<>/src/MD5Info/../system/system.hh:228:69: error: ISO C++17 does not allow dynamic exception specifications 228 | static std::string mkdtemp(std::string const& nameTemplate) throw(Problem); | ^ /<>/src/MD5Info/../system/system.hh:232:39: error: ISO C++17 does not allow dynamic exception specifications 232 | static std::string username() throw(Problem); | ^ In file included from /<>/src/MD5Info/MD5Info.ih:22, from /<>/src/MD5Info/save.cc:18: /<>/src/MD5Info/../system/system.hh:204:90: error: ISO C++17 does not allow dynamic exception specifications 204 | static int system(std::string const &command, bool simulate = Options::simulate) throw(Problem); | ^ In file included from /<>/src/MD5Info/MD5Info.ih:22, from /<>/src/MD
Bug#984022: coinor-symphony: ftbfs with GCC-11
Package: src:coinor-symphony
Version: 5.6.16+repack1-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/coinor-symphony_5.6.16+repack1-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
LP/lp_solver.c:2491:30: warning: statement will never be executed
[-Wswitch-unreachable]
2491 |printf("%c \n", sense[i]);
| ^
g++ -DHAVE_CONFIG_H -I. -I../include -I../include
-I../Applications/USER/include -I/usr/include/coin -I/usr/include/coin
-I/usr/include/coin -D__OSI_CLP__ -DUSE_CGL_CUTS -DSIGHANDLER -DHAS_RANDOM
-DHAS_SRANDOM -D__NONE__ -D__LINUX -DCOMPILE_IN_CG -DCOMPILE_IN_CP
-DCOMPILE_IN_LP -DCOMPILE_IN_TM -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -DSYMPHONY_BUILD -Wno-unknown-pragmas
-Wno-write-strings -Wno-sign-compare -Wno-cast-qual -c TreeManager/tm_func.c -o
libSym_la-tm_func.o >/dev/null 2>&1
TreeManager/tm_proccomm.c: In function 'void receive_node_desc(tm_prob*,
bc_node*)':
TreeManager/tm_proccomm.c:821:39: warning: '%i' directive writing between 1 and
11 bytes into a region of size between 0 and 49 [-Wformat-overflow=]
821 | sprintf(reason, "%s %i", reason, n->parent->bc_index
+ 1);
| ^~
TreeManager/tm_proccomm.c:821:35: note: directive argument in the range
[-2147483647, 2147483647]
821 | sprintf(reason, "%s %i", reason, n->parent->bc_index
+ 1);
| ^~~
In file included from /usr/include/stdio.h:867,
from TreeManager/tm_proccomm.c:17:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:34: note:
'__builtin___sprintf_chk' output between 3 and 62 bytes into a destination of
size 50
36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~
37 | __bos (__s), __fmt, __va_arg_pack ());
| ~
TreeManager/tm_proccomm.c:819:39: warning: '%i' directive writing 1 byte into a
region of size between 0 and 49 [-Wformat-overflow=]
819 | sprintf(reason, "%s %i", reason, 0);
| ^~
In file included from /usr/include/stdio.h:867,
from TreeManager/tm_proccomm.c:17:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:34: note:
'__builtin___sprintf_chk' output between 3 and 52 bytes into a destination of
size 50
36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~
37 | __bos (__s), __fmt, __va_arg_pack ());
| ~
TreeManager/tm_proccomm.c:832:36: warning: '%c' directive writing 1 byte into a
region of size between 0 and 49 [-Wformat-overflow=]
832 |sprintf(reason, "%s %c %f %f %i", reason, branch_dir,
|^~
TreeManager/tm_proccomm.c:832:32: note: assuming directive output of 8 bytes
832 |sprintf(reason, "%s %c %f %f %i", reason, branch_dir,
|^~~~
TreeManager/tm_proccomm.c:832:32: note: assuming directive output of 8 bytes
TreeManager/tm_proccomm.c:832:32: note: directive argument in the range [0,
2147483647]
In file included from /
Bug#984030: d-itg: ftbfs with GCC-11
Package: src:d-itg Version: 2.8.1-r1023-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/d-itg_2.8.1-r1023-4_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] |^~ newran2.cpp: In function ‘DividedRandom& operator/(Random&, Random&)’: newran2.cpp:1003:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1003 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1003:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1003 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(SelectedRandom&, SelectedRandom&)’: newran2.cpp:1121:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1121 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1121:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1121 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(AddedSelectedRandom&, SelectedRandom&)’: newran2.cpp:1128:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1128 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1128:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1128 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(SelectedRandom&, AddedSelectedRandom&)’: newran2.cpp:1135:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1135 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1135:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1135 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(AddedSelectedRandom&, AddedSelectedRandom&)’: newran2.cpp:1142:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1142 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1142:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1142 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In member function ‘SelectedRandom& Random::operator()(double)’: newran2.cpp:1148:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1148 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1148:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1148 |if (!r) ErrorNoSpace(); return *r; |^~ [ CXX ] myexcept.o <- myexcept.cpp [ CXX ] simpstr.o <- simpstr.cpp simpstr.cpp: In constructor ‘SimpleString::SimpleString(unsigned int, char)’: simpstr.cpp:46:4: warning: this ‘while’ clause does not guard... [-Wmisleading-indentation] 46 |while (i--) *s1++ = c; *s1 = 0; |^ simpstr.cpp:46:27: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘while’ 46 |while (i--) *s1++ = c; *s1 = 0; | ^ [ CXX ] extreal.o <- extreal.cpp [ AR ] libnewran.a <- newran1.o newran2.o myexcept.o simpstr.o extreal.o [ RL ] libnewran.a [ CX
Bug#984041: duma: ftbfs with GCC-11
Package: src:duma Version: 2.5.15-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/duma_2.5.15-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] createconf.c:169:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 169 | *( (unsigned long long int *) addr ) = 0L; |^ createconf.c:179:19: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 179 | TYPE addr = (TYPE)(buffer) + offset; | ^ createconf.c:182:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 182 | *( (unsigned char *) addr ) = 0; |^ createconf.c:183:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 183 | *( (unsigned short int*) addr ) = 0; |^ createconf.c:184:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 184 | *( (unsigned int *) addr ) = 0; |^ createconf.c:185:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 185 | *( (unsigned long int *) addr ) = 0L; |^ createconf.c:186:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 186 | *( (float *) addr ) = 0.0F; |^ createconf.c:187:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 187 | *( (double *)addr ) = 0.0; |^ createconf.c:188:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 188 | *( (long double *) addr ) = 0.0; |^ createconf.c:193:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 193 | *( (unsigned long long int *) addr ) = 0L; |^ rm -f createconf gcc -g -O0 -Wall -Wextra -DDUMA_SO_NO_LEAKDETECTION createconf.o -o createconf ./createconf make[2]: Leaving directory '/<>' g++ -g -O0 -Wall -Wextra -c dumapp.cpp -o dumapp.o In file included from dumapp.cpp:39: dumapp.h:88:49: error: ISO C++17 does not allow dynamic exception specifications 88 | void * DUMA_CDECL operator new(DUMA_SIZE_T) throw(std::bad_alloc); | ^ dumapp.h:98:51: error: ISO C++17 does not allow dynamic exception specifications 98 | void * DUMA_CDECL operator new[](DUMA_SIZE_T) throw(std::bad_alloc); | ^ dumapp.h:110:70: error: ISO C++17 does not allow dynamic exception specifications 110 | void * DUMA_CDECL operator new(DUMA_SIZE_T, const char *, int) throw(std::bad_alloc); | ^ dumapp.h:120:72: error: ISO C++17 does not allow dynamic exception specifications 120 | void * DUMA_CDECL operator new[](DUMA_SIZE_T, const char *, int) throw(std::bad_alloc); | ^ dumapp.cpp: In function ‘void* duma_new_operator(std::size_t, _DUMA_Allocator, bool, const char*, int)’: dumapp.cpp:167:21: warning: catching polymorphic type ‘class std::bad_alloc’ by value [-Wcatch-value=] 167 | catch (std::bad_alloc)// error occured in new_handler | ^ dumapp.cpp: At global scope: dumapp.cpp:328:1: error: ISO C++17 doe
Bug#984056: ifhp: ftbfs with GCC-11
Package: src:ifhp Version: 3.5.20-17 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/ifhp_3.5.20-17_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] ifhp.c:3023:17: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 3023 | if( filename ) SAFEFREE(filename); filename = 0; | ^~ ifhp.c:3023:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 3023 | if( filename ) SAFEFREE(filename); filename = 0; |^~~~ ifhp.c:3041:17: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 3041 | if( filename ) SAFEFREE(filename); filename = 0; | ^~ ifhp.c:3041:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 3041 | if( filename ) SAFEFREE(filename); filename = 0; |^~~~ ifhp.c:3057:9: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 3057 | if( filename ) SAFEFREE(filename); filename = 0; | ^~ ifhp.c:3057:44: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 3057 | if( filename ) SAFEFREE(filename); filename = 0; |^~~~ ifhp.c: In function ‘Send_job’: ifhp.c:4350:9: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 4350 | if( pgm ) SAFEFREE(pgm); pgm = 0; | ^~ ifhp.c:4350:34: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 4350 | if( pgm ) SAFEFREE(pgm); pgm = 0; | ^~~ ifhp.c:4527:33: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 4527 | if( pgm ) SAFEFREE(pgm); pgm = 0; | ^~ ifhp.c:4527:58: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 4527 | if( pgm ) SAFEFREE(pgm); pgm = 0; | ^~~ ifhp.c:4605:17: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 4605 | if( pgm ) SAFEFREE(pgm); pgm = 0; | ^~ ifhp.c:4605:42: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 4605 | if( pgm ) SAFEFREE(pgm); pgm = 0; | ^~~ ifhp.c: In function ‘Filter_file’: ifhp.c:5349:25: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 5349 | if(s) SAFEFREE(s); s = 0; | ^~ ifhp.c:5349:44: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 5349 | if(s) SAFEFREE(s); s = 0; |^ ifhp.c:5444:9: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] 5444 | if( orig_pgm ) SAFEFREE(orig_pgm); orig_pgm = 0; | ^~ ifhp.c:5444:44: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 5444 | if( orig_pgm ) SAFEFREE(orig_pgm); orig_pgm = 0;
Bug#984070: jaula: ftbfs with GCC-11
Package: src:jaula Version: 1.4.0-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/jaula_1.4.0-6_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c jaula_syntax_error.cc -o jaula_syntax_error.o >/dev/null 2>&1 jaula_parse.cc:459:22: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 459 | std::auto_ptrpItemVal(parseValue(lexan, token)); | ^~~~ In file included from /usr/include/c++/11/memory:76, from jaula_parse.cc:47: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ jaula_parse.cc: At global scope: jaula_parse.cc:563:5: error: ISO C++17 does not allow dynamic exception specifications 563 | throw(Exception) | ^ make[4]: *** [Makefile:617: jaula_parse.lo] Error 1 make[4]: *** Waiting for unfinished jobs In file included from jaula_value.cc:41: ../jaula/jaula_value.h:110:45: error: ISO C++17 does not allow dynamic exception specifications 110 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ ../jaula/jaula_value.h:130:43: error: ISO C++17 does not allow dynamic exception specifications 130 | Value &operator=(Value const &orig) throw(Bad_Data_Type); | ^ In file included from jaula_value.cc:42: ../jaula/jaula_value_array.h:151:45: error: ISO C++17 does not allow dynamic exception specifications 151 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ In file included from jaula_value.cc:43: ../jaula/jaula_value_boolean.h:98:45: error: ISO C++17 does not allow dynamic exception specifications 98 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ In file included from jaula_value.cc:44: ../jaula/jaula_value_null.h:83:45: error: ISO C++17 does not allow dynamic exception specifications 83 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ In file included from jaula_value.cc:45: ../jaula/jaula_value_number.h:98:45: error: ISO C++17 does not allow dynamic exception specifications 98 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ In file included from jaula_value.cc:46: ../jaula/jaula_value_number_int.h:99:45: error: ISO C++17 does not allow dynamic exception specifications 99 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ In file included from jaula_value.cc:47: ../jaula/jaula_value_object.h:154:45: error: ISO C++17 does not allow dynamic exception specifications 154 | virtual void set(Value const &origin) throw(Bad_Data_Type); | ^ ../jaula/jaula_value_object.h:172:9: error: ISO C++17 does not allow dynamic exception specifications 172 | throw(Name_Duplicated); | ^ In file included from jaula_value.cc:48: ../jaula/jaula_value_string.h:98:45: error
Bug#984083: lasi: ftbfs with GCC-11
Package: src:lasi Version: 1.1.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/lasi_1.1.0-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cmake_policy(SET CMP0003 NEW) endif(COMMAND cmake_policy) as early as possible but after the most recent call to cmake_minimum_required or cmake_policy(VERSION). This warning appears because target "example2" links to some libraries for which the linker must search: pango-1.0, gobject-2.0, glib-2.0, harfbuzz, pangoft2-1.0, pango-1.0 gobject-2.0, glib-2.0, harfbuzz, fontconfig, freetype, freetype, pango-1.0 gobject-2.0, glib-2.0, harfbuzz, pangoft2-1.0, pango-1.0, gobject-2.0 glib-2.0, harfbuzz, pangoft2-1.0, fontconfig, freetype, m and other libraries with known full path: /<>/obj-x86_64-linux-gnu/src/libLASi.so.0.0.1 CMake is adding directories in the second list to the linker search path in case they are needed to find libraries from the first list (for backwards compatibility with CMake 2.4). Set policy CMP0003 to OLD or NEW to enable or disable this behavior explicitly. Run "cmake --help-policy CMP0003" for more information. This warning is for project developers. Use -Wno-dev to suppress it. -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_C_COMPILER CMAKE_C_FLAGS -- Build files have been written to: /<>/obj-x86_64-linux-gnu /usr/bin/make -C obj-x86_64-linux-gnu make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/make -f CMakeFiles/documentation.dir/build.make CMakeFiles/documentation.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/documentation.dir/DependInfo.cmake --color= Scanning dependencies of target documentation make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' /usr/bin/make -f CMakeFiles/documentation.dir/build.make CMakeFiles/documentation.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make[3]: Nothing to be done for 'CMakeFiles/documentation.dir/build'. make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 15%] Built target documentation /usr/bin/make -f src/CMakeFiles/LASi.dir/build.make src/CMakeFiles/LASi.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src /<>/obj-x86_64-linux-gnu/src/CMakeFiles/LASi.dir/DependInfo.cmake --color= Scanning dependencies of target LASi make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' /usr/bin/make -f src/CMakeFiles/LASi.dir/build.make src/CMakeFiles/LASi.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 23%] Building CXX object src/CMakeFiles/LASi.dir/drawGlyph.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/g++ -DLASi_EXPORTS -I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/harfbuzz -I/usr/include/glib-2.0
Bug#984096: libcommoncpp2: ftbfs with GCC-11
Package: src:libcommoncpp2 Version: 1.8.1-10 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libcommoncpp2_1.8.1-10_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] | ^ ../inc/cc++/persist.h:476:53: note: in expansion of macro ‘THROWS’ 476 | __EXPORT Engine& operator >>( Engine& ar, bool& ob) THROWS (PersistException); | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:478:53: note: in expansion of macro ‘THROWS’ 478 | __EXPORT Engine& operator <<( Engine& ar, bool ob) THROWS (PersistException); | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:490:69: note: in expansion of macro ‘THROWS’ 490 | Engine& operator <<( Engine& ar, typename std::vector const& ob) THROWS (PersistException) | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:504:63: note: in expansion of macro ‘THROWS’ 504 | Engine& operator >>( Engine& ar, typename std::vector& ob) THROWS (PersistException) | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:521:68: note: in expansion of macro ‘THROWS’ 521 | Engine& operator <<( Engine& ar, typename std::deque const& ob) THROWS (PersistException) | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:535:62: note: in expansion of macro ‘THROWS’ 535 | Engine& operator >>( Engine& ar, typename std::deque& ob) THROWS (PersistException) | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:556:75: note: in expansion of macro ‘THROWS’ 556 | Engine& operator <<( Engine& ar, typename std::map const & ob) THROWS (PersistException) | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:570:68: note: in expansion of macro ‘THROWS’ 570 | Engine& operator >>( Engine& ar, typename std::map& ob) THROWS (PersistException) | ^~ ../inc/cc++/config.h:944:19: error: ISO C++17 does not allow dynamic exception specifications 944 | #define THROWS(x) throw(x) | ^ ../inc/cc++/persist.h:588:54: note: in expansion of macro ‘THROWS’ 588 | Engine& operator <<( Engine& ar, std::pair &ob) THROWS (Pers
Bug#984119: fbpager: ftbfs with GCC-11
Package: src:fbpager Version: 0.1.5~git20090221.1.8e0927e6-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/fbpager_0.1.5~git20090221.1.8e0927e6-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] In file included from FbPager.cc:38: Resources.hh: In member function ‘std::string FbTk::Resource::getString() [with T = FbPager::FbPager::Alignment]’: Resources.hh:72:1: warning: control reaches end of non-void function [-Wreturn-type] 72 | } | ^ mv -f .deps/fbpager-FbPager.Tpo .deps/fbpager-FbPager.Po x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I..-IFbTk -g -O2 -MT fbpager-Workspace.o -MD -MP -MF .deps/fbpager-Workspace.Tpo -c -o fbpager-Workspace.o `test -f 'Workspace.cc' || echo './'`Workspace.cc In file included from Workspace.hh:27, from Workspace.cc:24: FbTk/FbWindow.hh:208:10: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 208 | std::auto_ptr m_transparent; | ^~~~ In file included from /usr/include/c++/11/memory:76, from FbTk/FbWindow.hh:30, from Workspace.hh:27, from Workspace.cc:24: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ mv -f .deps/fbpager-Workspace.Tpo .deps/fbpager-Workspace.Po x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I..-IFbTk -g -O2 -MT fbpager-Ewmh.o -MD -MP -MF .deps/fbpager-Ewmh.Tpo -c -o fbpager-Ewmh.o `test -f 'Ewmh.cc' || echo './'`Ewmh.cc In file included from Ewmh.cc:22: Ewmh.hh:52:10: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 52 | std::auto_ptr m_data; | ^~~~ In file included from /usr/include/c++/11/memory:76, from Ewmh.hh:26, from Ewmh.cc:22: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from Ewmh.cc:28: FbTk/FbWindow.hh:208:10: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 208 | std::auto_ptr m_transparent; | ^~~~ In file included from /usr/include/c++/11/memory:76, from Ewmh.hh:26, from Ewmh.cc:22: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from Ewmh.cc:30: PropertyTools.hh:33:52: error: ISO C++17 does not allow dynamic exception specifications 33 | unsigned int getIntProperty(Window win, Atom atom) throw (PropertyException); |^ PropertyTools.hh:34:46: error: ISO C++17 does not allow dynamic exception specifications 34 | Window getWinProperty(Window win, Atom atom) throw (PropertyException); | ^ PropertyTools.hh:35:76: error: ISO C++17 does not allow dynamic exception specifications 35 | void getWinArrayProperty(Window win, Atom atom, std::vector &cont) throw (PropertyException); | ^ Ewmh.cc:56:14: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 56 | typedef std::auto_ptr PropTPtr; | ^~~
Bug#984159: gnubiff: ftbfs with GCC-11
Package: src:gnubiff Version: 2.2.17-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gnubiff_2.2.17-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 273 | GMutex *g_mutex_new (void); | ^~~ mailbox.cc:64:39: warning: ‘GMutex* g_mutex_new()’ is deprecated [-Wdeprecated-declarations] 64 | monitor_mutex_ = g_mutex_new (); | ^ In file included from /usr/include/glib-2.0/glib.h:111, from support.h:39, from mailbox.cc:33: /usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here 273 | GMutex *g_mutex_new (void); | ^~~ mailbox.cc: In copy constructor ‘Mailbox::Mailbox(const Mailbox&)’: mailbox.cc:83:31: warning: ‘GMutex* g_mutex_new()’ is deprecated [-Wdeprecated-declarations] 83 | mutex_ = g_mutex_new (); | ^ In file included from /usr/include/glib-2.0/glib.h:111, from support.h:39, from mailbox.cc:33: /usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here 273 | GMutex *g_mutex_new (void); | ^~~ mailbox.cc:84:39: warning: ‘GMutex* g_mutex_new()’ is deprecated [-Wdeprecated-declarations] 84 | monitor_mutex_ = g_mutex_new (); | ^ In file included from /usr/include/glib-2.0/glib.h:111, from support.h:39, from mailbox.cc:33: /usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here 273 | GMutex *g_mutex_new (void); | ^~~ mailbox.cc: In destructor ‘virtual Mailbox::~Mailbox()’: mailbox.cc:107:29: warning: ‘void g_mutex_free(GMutex*)’ is deprecated [-Wdeprecated-declarations] 107 | g_mutex_free (mutex_); | ^ In file included from /usr/include/glib-2.0/glib.h:111, from support.h:39, from mailbox.cc:33: /usr/include/glib-2.0/glib/deprecated/gthread.h:275:17: note: declared here 275 | voidg_mutex_free(GMutex *mutex); | ^~~~ mailbox.cc:110:37: warning: ‘void g_mutex_free(GMutex*)’ is deprecated [-Wdeprecated-declarations] 110 | g_mutex_free (monitor_mutex_); | ^ In file included from /usr/include/glib-2.0/glib.h:111, from support.h:39, from mailbox.cc:33: /usr/include/glib-2.0/glib/deprecated/gthread.h:275:17: note: declared here 275 | voidg_mutex_free(GMutex *mutex); | ^~~~ mailbox.cc: In static member function ‘static gboolean Mailbox::start_delayed_entry_point(gpointer)’: mailbox.cc:144:76: warning: ‘GThread* g_thread_create(GThreadFunc, gpointer, gboolean, GError**)’ is deprecated: Use 'g_thread_new' instead [-Wdeprecated-declarations] 144 | g_thread_create ((GThreadFunc) start_entry_point, data, false, &err); | ^ In file included from /usr/include/glib-2.0/glib.h:111, from support.h:39, from mailbox.cc:33: /usr/include/glib-2.0/glib/deprecated/gthread.h:100:10: note: declared here 100 | GThread *g_thread_create (GThreadFunc func, | ^
Bug#984180: htdig: ftbfs with GCC-11
Package: src:htdig Version: 1:3.2.0b6-18 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/htdig_3.2.0b6-18_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] In file included from WordDBPage.h:33, from WordDBCompress.cc:22: WordBitCompress.h:31:23: note: ‘typedef unsigned char byte’ 31 | typedef unsigned char byte; | ^~~~ In file included from WordDBCompress.cc:22: WordDBPage.h:387:15: error: ‘gotdata’ was not declared in this scope; did you mean ‘getdate’? 387 | byte *gotdata=new byte[len]; | ^~~ | getdate WordDBPage.h:387:27: error: reference to ‘byte’ is ambiguous 387 | byte *gotdata=new byte[len]; | ^~~~ In file included from /usr/include/c++/11/bits/stl_algobase.h:61, from /usr/include/c++/11/bits/char_traits.h:39, from /usr/include/c++/11/ios:40, from /usr/include/c++/11/ostream:38, from /usr/include/c++/11/iostream:39, from ../htlib/htString.h:23, from ../htlib/HtPack.h:26, from WordRecord.h:43, from WordDBPage.h:34, from WordDBCompress.cc:22: /usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’ 404 | enum class byte : unsigned char; | ^~~~ In file included from WordDBPage.h:33, from WordDBCompress.cc:22: WordBitCompress.h:31:23: note: ‘typedef unsigned char byte’ 31 | typedef unsigned char byte; | ^~~~ In file included from WordDBCompress.cc:22: WordDBPage.h:392:19: error: type ‘’ argument given to ‘delete’, expected pointer 392 | delete [] gotdata; | ^~~ WordDBPage.h: In constructor ‘WordDBPage::WordDBPage(int)’: WordDBPage.h:491:25: error: reference to ‘byte’ is ambiguous 491 | pg=(PAGE *)(new byte[pgsz]); | ^~~~ In file included from /usr/include/c++/11/bits/stl_algobase.h:61, from /usr/include/c++/11/bits/char_traits.h:39, from /usr/include/c++/11/ios:40, from /usr/include/c++/11/ostream:38, from /usr/include/c++/11/iostream:39, from ../htlib/htString.h:23, from ../htlib/HtPack.h:26, from WordRecord.h:43, from WordDBPage.h:34, from WordDBCompress.cc:22: /usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’ 404 | enum class byte : unsigned char; | ^~~~ In file included from WordDBPage.h:33, from WordDBCompress.cc:22: WordBitCompress.h:31:23: note: ‘typedef unsigned char byte’ 31 | typedef unsigned char byte; | ^~~~ In file included from WordDBCompress.cc:22: WordDBPage.h:491:29: error: expected ‘)’ before ‘[’ token 491 | pg=(PAGE *)(new byte[pgsz]); | ^ WordDBPage.h:491:20: note: to match this ‘(’ 491 | pg=(PAGE *)(new byte[pgsz]); |^ make[2]: *** [Makefile:523: WordDBCompress.lo] Error 1 make[2]: Leaving directory '/<>/htword' make[1]: *** [Makefile:451: all-recursive] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:20: build-stamp] Error 2 dpkg-buildp
Bug#984186: libloki: ftbfs with GCC-11
Package: src:libloki Version: 0.1.7-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libloki_0.1.7-4_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] | ^~~~ In file included from /usr/include/c++/11/memory:76, from ../include/loki/Singleton.h:30, from ../include/loki/SmallObj.h:23, from SmallObj.cpp:19: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from SmallObj.cpp:19: ../include/loki/SmallObj.h: At global scope: ../include/loki/SmallObj.h:462:57: error: ISO C++17 does not allow dynamic exception specifications 462 | static void * operator new ( std::size_t size ) throw ( std::bad_alloc ) | ^ In file included from ../include/loki/SmallObj.h:23, from ../include/loki/SmartPtr.h:33, from SmartPtr.cpp:20: ../include/loki/Singleton.h: In function ‘void Loki::SetLongevity(T*, unsigned int, Destroyer)’: ../include/loki/Singleton.h:158:14: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 158 | std::auto_ptr | ^~~~ In file included from /usr/include/c++/11/memory:76, from ../include/loki/Singleton.h:30, from ../include/loki/SmallObj.h:23, from ../include/loki/SmartPtr.h:33, from SmartPtr.cpp:20: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from ../include/loki/SmallObj.h:23, from ../include/loki/SmartPtr.h:33, from ../include/loki/StrongPtr.h:20, from StrongPtr.cpp:16: ../include/loki/Singleton.h: In function ‘void Loki::SetLongevity(T*, unsigned int, Destroyer)’: ../include/loki/Singleton.h:158:14: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 158 | std::auto_ptr | ^~~~ In file included from /usr/include/c++/11/memory:76, from ../include/loki/Singleton.h:30, from ../include/loki/SmallObj.h:23, from ../include/loki/SmartPtr.h:33, from ../include/loki/StrongPtr.h:20, from StrongPtr.cpp:16: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from ../include/loki/SmartPtr.h:33, from ../include/loki/StrongPtr.h:20, from StrongPtr.cpp:16: ../include/loki/SmallObj.h: At global scope: ../include/loki/SmallObj.h:462:57: error: ISO C++17 does not allow dynamic exception specifications 462 | static void * operator new ( std::size_t size ) throw ( std::bad_alloc ) | ^ In file included from ../include/loki/SmartPtr.h:33, from SmartPtr.cpp:20: ../include/loki/SmallObj.h: At global scope: ../include/loki/SmallObj.h:462:57: error: ISO C++17 does not allow dynamic exception specifications 462 | static void * operator new ( std::size_t size ) throw ( std::bad_alloc ) | ^ make[3]: ***
Bug#984196: libopendbx: ftbfs with GCC-11
Package: src:libopendbx Version: 1.4.6-15 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libopendbx_1.4.6-15_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 193 | unsigned long Result_Impl::columnPos( const string& name ) throw( std::exception ) |^ odbx_impl.cpp:216:67: error: ISO C++17 does not allow dynamic exception specifications 216 | const string Result_Impl::columnName( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:233:63: error: ISO C++17 does not allow dynamic exception specifications 233 | odbxtype Result_Impl::columnType( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:245:69: error: ISO C++17 does not allow dynamic exception specifications 245 | unsigned long Result_Impl::fieldLength( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:257:66: error: ISO C++17 does not allow dynamic exception specifications 257 | const char* Result_Impl::fieldValue( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:268:61: error: ISO C++17 does not allow dynamic exception specifications 268 | Lob_Iface* Result_Impl::getLob( const char* value ) throw( std::exception ) | ^ odbx_impl.cpp:283:48: error: ISO C++17 does not allow dynamic exception specifications 283 | Stmt_Impl::Stmt_Impl( odbx_t* handle ) throw( std::exception ) |^ odbx_impl.cpp:304:79: error: ISO C++17 does not allow dynamic exception specifications 304 | StmtSimple_Impl::StmtSimple_Impl( odbx_t* handle, const string& sql ) throw( std::exception ) : Stmt_Impl( handle ) | ^ odbx_impl.cpp:329:44: error: ISO C++17 does not allow dynamic exception specifications 329 | StmtSimple_Impl::StmtSimple_Impl() throw( std::exception ) : Stmt_Impl( NULL ) |^ odbx_impl.cpp:368:50: error: ISO C++17 does not allow dynamic exception specifications 368 | Result_Iface* StmtSimple_Impl::execute() throw( std::exception ) | ^ odbx_impl.cpp:380:55: error: ISO C++17 does not allow dynamic exception specifications 380 | inline void StmtSimple_Impl::_exec_noparams() throw( std::exception ) | ^ odbx_impl.cpp:455:89: error: ISO C++17 does not allow dynamic exception specifications 455 | Conn_Impl::Conn_Impl( const char* backend, const char* host, const char* port ) throw( std::exception ) | ^ odbx_impl.cpp:483:106: error: ISO C++17 does not allow dynamic exception specifications 483 | void Conn_Impl::bind( const char* database, const char* who, const char* cred, odbxbind method ) throw( std::exception ) |
Bug#984211: libwibble: ftbfs with GCC-11
Package: src:libwibble Version: 1.1-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libwibble_1.1-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] make -f wibble/CMakeFiles/wibble.dir/build.make wibble/CMakeFiles/wibble.dir/build make[4]: Entering directory '/<>/debian/build' [ 1%] Building CXX object wibble/CMakeFiles/wibble.dir/exception.o [ 2%] Building CXX object wibble/CMakeFiles/wibble.dir/string.o [ 3%] Building CXX object wibble/CMakeFiles/wibble.dir/regexp.o cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. -I/<>/debian/build/wibble/.. -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/wibble.dir/exception.o -c /<>/wibble/exception.cpp cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. -I/<>/debian/build/wibble/.. -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/wibble.dir/string.o -c /<>/wibble/string.cpp cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. -I/<>/debian/build/wibble/.. -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/wibble.dir/regexp.o -c /<>/wibble/regexp.cpp [ 4%] Building CXX object wibble/CMakeFiles/wibble.dir/test.o cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. -I/<>/debian/build/wibble/.. -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/wibble.dir/test.o -c /<>/wibble/test.cpp In file included from /<>/wibble/regexp.cpp:21: /<>/wibble/../wibble/regexp.h:66:77: error: ISO C++17 does not allow dynamic exception specifications 66 | Regexp(const std::string& expr, int match_count = 0, int flags = 0) throw (wibble::exception::Regexp); | ^ /<>/wibble/../wibble/regexp.h:69:59: error: ISO C++17 does not allow dynamic exception specifications 69 | bool match(const std::string& str, int flags = 0) throw (wibble::exception::Regexp); | ^ /<>/wibble/../wibble/regexp.h:75:41: error: ISO C++17 does not allow dynamic exception specifications 75 | std::string operator[](int idx) throw (wibble::exception::OutOfRange); | ^ /<>/wibble/../wibble/regexp.h:77:36: error: ISO C++17 does not allow dynamic exception specifications 77 | size_t matchStart(int idx) throw (wibble::exception::OutOfRange); |^ /<>/wibble/../wibble/regexp.h:78:34: error: ISO C++17 does not allow dynamic exception specifications 78 | size_t matchEnd(int idx) throw (wibble::exception::OutOfRange); | ^ /<>/wibble/../wibble/regexp.h:79:37: error: ISO C++17 does not allow dynamic exception specifications 79 | size_t matchLength(int idx) throw (wibble::exception::OutOfRange); | ^ /<>/wibble/../wibbl
Bug#984262: o3dgc: ftbfs with GCC-11
Package: src:o3dgc
Version: 0~20131011-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/o3dgc_0~20131011-4_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
|
^
[ 80%] Linking CXX static library libo3dgc_dec_lib.a
make[4]: Leaving directory '/<>/src'
[ 80%] Built target o3dgc_dec_lib
make[4]: Entering directory '/<>/src'
Scanning dependencies of target test_o3dgc
make[4]: Leaving directory '/<>/src'
make[4]: Entering directory '/<>/src'
[ 90%] Building CXX object test/CMakeFiles/test_o3dgc.dir/src/main.cpp.o
In file included from /<>/src/test/src/main.cpp:37:
/<>/src/test/../o3dgc_decode_lib/inc/o3dgcSC3DMCDecoder.h: In
member function ‘o3dgc::O3DGCErrorCode
o3dgc::SC3DMCDecoder::SetIterator(long unsigned int)’:
/<>/src/test/../o3dgc_decode_lib/inc/o3dgcSC3DMCDecoder.h:66:97:
warning: no return statement in function returning non-void [-Wreturn-type]
66 | O3DGCErrorCode SetIterator(unsigned long iterator)
{ m_iterator = iterator;}
|
^
In file included from /<>/src/test/src/main.cpp:41:
/<>/src/test/../o3dgc_decode_lib/inc/o3dgcDynamicVectorDecoder.h:
In member function ‘o3dgc::O3DGCErrorCode
o3dgc::DynamicVectorDecoder::SetIterator(long unsigned int)’:
/<>/src/test/../o3dgc_decode_lib/inc/o3dgcDynamicVectorDecoder.h:54:97:
warning: no return statement in function returning non-void [-Wreturn-type]
54 | O3DGCErrorCode SetIterator(unsigned long iterator)
{ m_iterator = iterator;}
|
^
/<>/src/test/src/main.cpp: In function ‘int
testDynamicVectorCompression()’:
/<>/src/test/src/main.cpp:517:23: warning: comparison of integer
expressions of different signedness: ‘long int’ and ‘const long unsigned int’
[-Wsign-compare]
517 | for(long n = 0; n < N; ++n)
| ~~^~~
/<>/src/test/src/main.cpp:510:25: warning: unused variable ‘S’
[-Wunused-variable]
510 | const unsigned long S = D*N;
| ^
/<>/src/test/src/main.cpp: In function ‘bool LoadIFS(const
string&, std::vector >&, std::vector >&,
std::vector >&, std::vector
>&, std::vector&)’:
/<>/src/test/src/main.cpp:1158:42: warning: unused variable ‘p’
[-Wunused-variable]
1158 | for(unsigned long i = 0, p = 0; i < n; ++i)
| ^
/<>/src/test/src/main.cpp:1168:42: warning: unused variable ‘p’
[-Wunused-variable]
1168 | for(unsigned long i = 0, p = 0; i < n; ++i)
| ^
/<>/src/test/src/main.cpp:1181:42: warning: unused variable ‘p’
[-Wunused-variable]
1181 | for(unsigned long i = 0, p = 0; i < n; ++i)
| ^
/<>/src/test/src/main.cpp:1194:42: warning: unused variable ‘p’
[-Wunused-variable]
1194 | for(unsigned long i = 0, p = 0; i < n; ++i)
| ^
/<>/src/test/src/main.cpp:1209:46: warning: unused variable ‘p’
[-Wunused-variable]
1209 | for(unsigned long i = 0, p = 0; i < n; ++i)
| ^
In file included from
/<>/src/test/../o3dgc_decode_lib/inc/o3dgcSC3DMCDecoder.h:109,
from /<>/src/test/
Bug#984267: omnievents: ftbfs with GCC-11
Package: src:omnievents Version: 1:2.6.2-5.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/omnievents_2.6.2-5.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from ProxyPushConsumer.cc:25: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC ProxyPushSupplier.cc In file included from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: EventQueue.h:93:3: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 93 | auto_ptr _filter; | ^~~~ In file included from /usr/include/c++/11/memory:76, from EventQueue.h:34, from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: EventQueue.h: In member function ‘void OmniEvents::EventQueue::setFilter(OmniEvents::Filter*)’: EventQueue.h:74:5: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 74 | auto_ptr f(filter); | ^~~~ In file included from /usr/include/c++/11/memory:76, from EventQueue.h:34, from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC Servant.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC SupplierAdmin.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC omniEventsLog.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC version.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC getopt.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security
Bug#984269: omniorb-dfsg: ftbfs with GCC-11
Package: src:omniorb-dfsg Version: 4.2.2-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/omniorb-dfsg_4.2.2-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] g++ -M -MD -MG -p static/ -p shared/ -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../../../../../src/lib/omniORB/orbcore/.. -I../../../../include/omniORB4/internal -I../../../../../include/omniORB4/internal -D_REENTRANT -DUSE_omniORB_logStream -D_OMNIORB_LIBRARY -DOMNIORB_VERSION_STRING="4.2.2" -DOMNIORB_VERSION_HEX=0x040202F1 -DCONFIG_DEFAULT_LOCATION="/etc/omniORB.cfg" -DCONFIG_ENV="OMNIORB_CONFIG" -DUnixArchitecture -I. -I../../../../../src/lib/omniORB/orbcore -I../../../../include -I../../../../../include -D__OSVERSION__=2 -D__linux__ -D__x86_64__ ../../../../../src/lib/omniORB/orbcore/unix/unixActive.cc ../../../../../src/lib/omniORB/orbcore/unix/unixAddress.cc ../../../../../src/lib/omniORB/orbcore/unix/unixEndpoint.cc ../../../../../src/lib/omniORB/orbcore/unix/unixConnection.cc ../../../../../src/lib/omniORB/orbcore/unix/unixTransportImpl.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpActive.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpAddress.cc ../../../../../src/lib/omniOR B/orbcore/tcp/tcpEndpoint.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpConnection.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpTransportImpl.cc ../../../../../src/lib/omniORB/orbcore/tcpSocket.cc ../../../../../src/lib/omniORB/orbcore/Namingstub.cc ../../../../../src/lib/omniORB/orbcore/poastubs.cc ../../../../../src/lib/omniORB/orbcore/objectStub.cc ../../../../../src/lib/omniORB/orbcore/bootstrapstub.cc ../../../../../src/lib/omniORB/orbcore/cs-UTF-16.cc ../../../../../src/lib/omniORB/orbcore/cs-UTF-8.cc ../../../../../src/lib/omniORB/orbcore/cs-8859-1.cc ../../../../../src/lib/omniORB/orbcore/cs-16bit.cc ../../../../../src/lib/omniORB/orbcore/cs-8bit.cc ../../../../../src/lib/omniORB/orbcore/codeSets.cc ../../../../../src/lib/omniORB/orbcore/SocketCollection.cc ../../../../../src/lib/omniORB/orbcore/giopMonitor.cc ../../../../../src/lib/omniORB/orbcore/giopBiDir.cc ../../../../../src/lib/omniORB/orbcore/giopImpl12.cc ../../../../../src/lib/omniORB/orbcore/giopImpl11.cc .. /../../../../src/lib/omniORB/orbcore/giopImpl10.cc ../../../../../src/lib/omniORB/orbcore/giopStreamImpl.cc ../../../../../src/lib/omniORB/orbcore/GIOP_S.cc ../../../../../src/lib/omniORB/orbcore/GIOP_C.cc ../../../../../src/lib/omniORB/orbcore/giopRendezvouser.cc ../../../../../src/lib/omniORB/orbcore/giopWorker.cc ../../../../../src/lib/omniORB/orbcore/giopServer.cc ../../../../../src/lib/omniORB/orbcore/giopStream.cc ../../../../../src/lib/omniORB/orbcore/giopStrand.cc ../../../../../src/lib/omniORB/orbcore/giopRope.cc ../../../../../src/lib/omniORB/orbcore/giopEndpoint.cc ../../../../../src/lib/omniORB/orbcore/cdrValueChunkStream.cc ../../../../../src/lib/omniORB/orbcore/cdrMemoryStream.cc ../../../../../src/lib/omniORB/orbcore/cdrStreamAdapter.cc ../../../../../src/lib/omniORB/orbcore/cdrStream.cc ../../../../../src/lib/omniORB/orbcore/omniTransport.cc ../../../../../src/lib/omniORB/orbcore/omniPolicy.cc ../../../../../src/lib/omniORB/orbcore/uri.cc ../../../../../src/lib/omniO RB/orbcore/rmutex.cc ../../../../../src/lib/omniORB/orbcore/transportRules.cc ../../../../../src/lib/omniORB/orbcore/tracedthread.cc ../../../../../src/lib/omniORB/orbcore/callHandle.cc ../../../../../src/lib/omniORB/orbcore/shutdownIdentity.cc ../../../../../src/lib/omniORB/orbcore/inProcessIdentity.cc ../../../../../src/lib/
Bug#984274: openclonk: ftbfs with GCC-11
Package: src:openclonk Version: 8.1-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/openclonk_8.1-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /<>/src/script/C4AulCompiler.cpp:1100:31: warning: this statement may fall through [-Wimplicit-fallthrough=] 1100 | AddBCC(n->loc, AB_CFUNCTION, reinterpret_cast(v._getFunction())); | ~~^~~~ /<>/src/script/C4AulCompiler.cpp:1101:17: note: here 1101 | default: | ^~~ make[3]: Leaving directory '/<>/build' [ 15%] Built target c4group [ 17%] Building CXX object CMakeFiles/libc4script.dir/src/script/C4AulFunc.cpp.o /usr/bin/c++ -DCOMPILED_AS_C4LIBRARY -DHAVE_CONFIG_H -DNDEBUG -DOC_SYSTEM_DATA_DIR=\"/usr/share/games/openclonk\" -I/<>/build -I/<> -I/<>/build/libc4script_autogen/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/<>/src -isystem /usr/include/SDL2 -isystem /<>/thirdparty -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall -Wextra -Wredundant-decls -Wendif-labels -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Winit-self -Wsign-promo -Wno-reorder -Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wformat-security -std=gnu++14 -o CMakeFiles/libc4script.dir/src/script/C4AulFunc.cpp.o -c /<>/src/script/C4AulFunc.cpp /<>/src/script/C4AulExec.cpp: In member function ‘void C4AulProfiler::Show()’: /<>/src/script/C4AulExec.cpp:1004:36: warning: typedef ‘EntryList’ locally defined but not used [-Wunused-local-typedefs] 1004 | typedef std::vector EntryList; |^ [ 17%] Building CXX object CMakeFiles/libc4script.dir/src/script/C4AulLink.cpp.o /usr/bin/c++ -DCOMPILED_AS_C4LIBRARY -DHAVE_CONFIG_H -DNDEBUG -DOC_SYSTEM_DATA_DIR=\"/usr/share/games/openclonk\" -I/<>/build -I/<> -I/<>/build/libc4script_autogen/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/<>/src -isystem /usr/include/SDL2 -isystem /<>/thirdparty -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall -Wextra -Wredundant-decls -Wendif-labels -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Winit-self -Wsign-promo -Wno-reorder -Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wformat-security -std=gnu++14 -o CMakeFiles/libc4script.dir/src/script/C4AulLink.cpp.o -c /<>/src/script/C4AulLink.cpp [ 17%] Building CXX object CMakeFiles/libc4script.dir/src/script/C4AulParse.cpp.o /usr/bin/c++ -DCOMPILED_AS_C4LIBRARY -DHAVE_CONFIG_H -DNDEBUG -DOC_SYSTEM_DATA_DIR=\"/usr/share/games/openclonk\" -I/<>/build -I/<> -I/<>/build/libc4script_autogen/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/<>/src -isystem /usr/include/SDL2 -isystem /<>/thirdparty -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall -Wextra -Wredundant-decls -Wendif-labels -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Winit-self -Wsign-promo -Wno-reorder -Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wformat-security -std=gnu++14 -o CMakeFiles/libc4script.dir/src/script/C4AulParse.cpp.o -c /<>/src/script/C4AulParse.cpp [ 17%] Building CXX object CMakeFiles/libc4script.dir/src/script/C4AulScriptFunc.cpp.o
Bug#984344: spamprobe: ftbfs with GCC-11
Package: src:spamprobe Version: 1.4d-14 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/spamprobe_1.4d-14_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] checking for png.h... yes checking for png_set_progressive_read_fn in -lpng... yes checking jpeglib.h usability... yes checking jpeglib.h presence... yes checking for jpeglib.h... yes checking for jpeg_read_header in -ljpeg... yes checking for a BSD-compatible install... /usr/bin/install -c configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/database/Makefile config.status: creating src/hdl/Makefile config.status: creating src/includes/Makefile config.status: creating src/input/Makefile config.status: creating src/parser/Makefile config.status: creating src/utility/Makefile config.status: creating src/spamprobe/Makefile config.status: executing depfiles commands make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' Making all in database make[4]: Entering directory '/<>/src/database' g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"spamprobe\" -DVERSION=\"1.4d\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_REGEX_H=1 -DUSE_8BIT=1 -DUSE_CDB=1 -DUSE_DB=1 -DUSE_MMAP=1 -DHAVE_UNGIF=1 -DHAVE_PNG=1 -DHAVE_JPEG=1 -I. -I. -I../../src/includes -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o CleanupManager.o CleanupManager.cc g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"spamprobe\" -DVERSION=\"1.4d\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_REGEX_H=1 -DUSE_8BIT=1 -DUSE_CDB=1 -DUSE_DB=1 -DUSE_MMAP=1 -DHAVE_UNGIF=1 -DHAVE_PNG=1 -DHAVE_JPEG=1 -I. -I. -I../../src/includes -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o DatabaseConfig.o DatabaseConfig.cc In file included from FrequencyDBImpl_hash.h:37, from DatabaseConfig.cc:37: HashDataFile.h: In member function ‘bool HashDataFile::isReadOnly() const’: HashDataFile.h:97:3: warning: no return statement in function returning non-void [-Wreturn-type] 97 | } | ^ g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"spamprobe\" -DVERSION=\"1.4d\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_REGEX_H=1 -DUSE_8BIT=1 -DUSE_CDB=1 -DUSE_DB=1 -DUSE_MMAP=1 -DHAVE_UNGIF=1 -DHAVE_PNG=1 -DHAVE_JPEG=1 -I. -I. -I../../src/includes -DNDEBUG -Wdate-time -D_
Bug#984361: tcm: ftbfs with GCC-11
Package: src:tcm Version: 2.20+TSQD-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/tcm_2.20+TSQD-6_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from modejunction.h:25, from modejunction.c:22: /<>/src/gl/llist.h: In member function ‘int List::next()’: /<>/src/gl/llist.h:106:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h:106:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h: In member function ‘int List::prev()’: /<>/src/gl/llist.h:110:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 110 | if (current) current=current->prev; return (current != 0); } | ^~ /<>/src/gl/llist.h:110:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 110 | if (current) current=current->prev; return (current != 0); } | ^~ /usr/bin/g++ -Wall -g -fcommon -O2 -DCONFIG_INSTALL=\"/etc/tcm/\" -DTCM_INSTALL_DIR=\"/usr\" -DTCM_INSTALL_LIB=\"/usr/lib/\" -DTCM_INSTALL_SHARE=\"/usr/share/doc/tcm-doc/\" -DCONFIG_FILE=\"tcm.conf\" -DHELP_DIR=\"/usr/share/doc/tcm-doc/help/\" -DCOLOR_FILE=\"colorrgb.txt\" -DBANNER_FILE=\"banner.ps\" -I. -I/<>/src/bitmaps -I/<>/src/gl -I/<>/src/ui -I/<>/src/ed -I/<>/src/dg -I/<>/src/tb -I/usr/X11R6/LessTif/Motif1.2/include -I/usr/X11R6/include -I/usr/X11R6/include/X11 -I../dv -DLINUX -c cbactor.c In file included from /<>/src/dg/thing.h:25, from /<>/src/dg/subject.h:25, from /<>/src/dg/node.h:25, from cbactor.h:26, from cbactor.c:23: /<>/src/gl/llist.h: In member function ‘int List::next()’: /<>/src/gl/llist.h:106:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h:106:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h: In member function ‘int List::prev()’: /<>/src/gl/llist.h:110:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 110 | if (current) current=current->prev; return (current != 0); } | ^~ /<>/src/gl/llist.h:110:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 110 | if (current) current=current->prev; return (current != 0); } | ^~ /usr/bin/g++ -Wall -g -fcommon -O2 -DCONFIG_INSTALL=\"/etc/tcm/\" -DTCM_INSTALL_DIR=\"/usr\" -DTCM_INSTALL_LIB=\"/usr/lib/\" -DTCM_INSTALL_SHARE=\"/usr/share/doc/tcm-doc/\" -DCONFIG_FILE=\"tcm.conf\" -DHELP_DIR=\"/usr/share/doc/tcm-doc/help/\" -DCOLOR_FILE=\"colorrgb.txt\" -DBANNER_FILE=\"banner.ps\" -I. -I/<>/src/bitmaps -I/<>/src/gl -I/<>/src/ui -I/<>/src/ed -I/<>/src/dg -I/<>/
Bug#984409: wvdial: ftbfs with GCC-11
Package: src:wvdial
Version: 1.61-5
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/wvdial_1.61-5_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-987b09b1-c7f3-49b4-b77e-1f236fc11dc7
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package wvdial
dpkg-buildpackage: info: source version 1.61-5
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Gianfranco Costamagna
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh_testdir
dh_testroot
debconf-updatepo
rm -f build-stamp
[ ! -f Makefile ] || /usr/bin/make clean
dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level 7 in
use)
debian/rules build
dh_testdir
./configure
dh_auto_build --buildsystem=makefile -- CXXOPTS="-fno-implement-inlines
-fno-exceptions" VERBOSE=1
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 7
in use)
make -j1 "CXXOPTS=-fno-implement-inlines -fno-exceptions" VERBOSE=1
make[1]: Entering directory '/<>'
* Generating CC
* Generating CXX
./CXX -c wvdialer
In file included from /usr/include/termios.h:25,
from wvdialer.h:12,
from wvdialer.cc:9:
/usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
_DEFAULT_SOURCE"
| ^~~
In file included from /usr/include/wvstreams/unihashtree.h:12,
from /usr/include/wvstreams/uniconftree.h:11,
from /usr/include/wvstreams/uniconfroot.h:11,
from /usr/include/wvstreams/wvconfemu.h:10,
from wvdialer.h:15,
from wvdialer.cc:9:
/usr/include/wvstreams/wvscatterhash.h: In member function ‘unsigned char*
WvScatterHash::Iter::getstatus()’:
/usr/include/wvstreams/wvscatterhash.h:186:46: error: invalid use of non-static
data member ‘WvScatterHashBase::xstatus’
186 | unsigned char *getstatus() { return &xstatus[index-1]; }
| ^~~
/usr/include/wvstreams/wvscatterhash.h:90:13: note: declared here
90 | Status *xstatus;
| ^~~
In file included from /usr/include/wvstreams/wvcallbacklist.h:9,
from /usr/include/wvstreams/uniconfgen.h:11,
from /usr/include/wvstreams/uniconf.h:12,
from /usr/include/wvstreams/uniconfroot.h:10,
from /usr/include/wvstreams/wvconfemu.h:10,
from wvdialer.h:15,
from wvdialer.cc:9:
/usr/include/wvstreams/wvconfemu.h: In constructor
‘WvConfigSectionEmu::Iter::Iter(WvConfigSectionEmu&)’:
/usr/include/wvstreams/wvconfemu.h:85:16: warning: the compiler can assume that
the address of ‘_sect’ will never be NULL [-Waddress]
85 | assert(&_sect);
|^~
make[1]: *** [wvrules.mk:142: wvdialer.o] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j1 "CXXOPTS=-fno-implement-inlines -fno-exceptions"
VERBOSE=1 returned exit code 2
make: *** [debian/rules:15: build-stamp] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Bug#984420: wvstreams: ftbfs with GCC-11
Package: src:wvstreams Version: 4.6.1-15 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/wvstreams_4.6.1-15_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ utils/wvbufferstore.cc: In member function ‘void MemOps::swap(void*, void*, size_t)’: utils/wvbufferstore.cc:47:33: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister] 47 | register unsigned char *t1 = (unsigned char*)target; | ^~ utils/wvbufferstore.cc:48:33: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister] 48 | register unsigned char *t2 = (unsigned char*)source; | ^~ utils/wvbufferstore.cc:51:36: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister] 51 | register unsigned char temp; |^~~~ ./CXX -c utils/wvcont x86_64-linux-gnu-g++ -c -o utils/wvcont.o utils/wvcont.cc -MMD -MF utils/.wvcont.d -MP -MQ utils/wvcont.o -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/tcl8.3 -DDEBUG=0 -I./include -D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DUNSTABLE -fPIC -Wall -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-tree-dce -fno-optimize-sibling-calls -fPIC -DPIC -fno-tree-dce -fno-optimize-sibling-calls -Wall -Woverloaded-virtual In file included from /usr/include/unistd.h:25, from ./include/wvxplc.h:20, from ./include/wvtypetraits.h:10, from ./include/wvlinklist.h:10, from ./include/wvcont.h:15, from utils/wvcont.cc:8: /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ ./CXX -c utils/wverror x86_64-linux-gnu-g++ -c -o utils/wverror.o utils/wverror.cc -MMD -MF utils/.wverror.d -MP -MQ utils/wverror.o -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/tcl8.3 -DDEBUG=0 -I./include -D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DUNSTABLE -fPIC -Wall -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-tree-dce -fno-optimize-sibling-calls -fPIC -DPIC -fno-tree-dce -fno-optimize-sibling-calls -Wall -Woverloaded-virtual In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/string.h:26, from ./include/wvstring.h:18, from ./include/wverror.h:10, from utils/wverror.cc:7: /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ ./CXX -c streams/wvfdstream x86_64-linux-gnu-g++ -c -o streams/wvfdstream.o streams/wvfdstream.cc -MMD -MF streams/.wvfdstream.d -MP -MQ streams/wvfdstream.o -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/tcl8.3 -DDEBUG=0 -I./include -D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
Bug#984434: id3ren: Wrong homepage
Package: id3ren Version: 1.1b0-7 Severity: normal I have see that the project homepage do not respond anymore: http://cbothamy.free.fr/projects/id3ren/ I think that the homepage is now: https://github.com/sebcode/id3ren Ciao Davide Note: this is a simplified bug report that I use to report homepage problems found at https://repology.org/repository/debian_testing/problems
