Your message dated Mon, 11 Oct 2021 12:15:01 +0000
with message-id <e1mzucr-0005in...@fasolo.debian.org>
and subject line Bug#984181: fixed in htmlcxx 0.87-2
has caused the Debian Bug report #984181,
regarding htmlcxx: ftbfs with GCC-11
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.)


-- 
984181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:htmlcxx
Version: 0.87-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/htmlcxx_0.87-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.

[...]
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for main in -lfl... no
checking for iconv_open in -liconv... no
checking for ANSI C header files... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking if there is spoon... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating html/Makefile
config.status: creating css/Makefile
config.status: creating htmlcxx.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
   dh_auto_build
        make -j4
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make  all-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>'
Making all in html
make[3]: Entering directory '/<<PKGBUILDDIR>>/html'
g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DDEFAULT_CSS="\"/usr/share/htmlcxx/css/default.css\"" 
-c -o tests.o tests.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DDEFAULT_CSS="\"/usr/share/htmlcxx/css/default.css\"" -c -o 
libhtmlcxx_la-ParserSax.lo `test -f 'ParserSax.cc' || echo './'`ParserSax.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DDEFAULT_CSS="\"/usr/share/htmlcxx/css/default.css\"" -c -o 
libhtmlcxx_la-ParserDom.lo `test -f 'ParserDom.cc' || echo './'`ParserDom.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DDEFAULT_CSS="\"/usr/share/htmlcxx/css/default.css\"" -c -o 
libhtmlcxx_la-Extensions.lo `test -f 'Extensions.cc' || echo './'`Extensions.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DDEFAULT_CSS=\"/usr/share/htmlcxx/css/default.css\" -c 
ParserSax.cc  -fPIC -DPIC -o .libs/libhtmlcxx_la-ParserSax.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DDEFAULT_CSS=\"/usr/share/htmlcxx/css/default.css\" -c 
ParserDom.cc  -fPIC -DPIC -o .libs/libhtmlcxx_la-ParserDom.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DDEFAULT_CSS=\"/usr/share/htmlcxx/css/default.css\" -c 
Extensions.cc  -fPIC -DPIC -o .libs/libhtmlcxx_la-Extensions.o
In file included from tests.cc:6:
CharsetConverter.h:20:90: error: ISO C++17 does not allow dynamic exception 
specifications
   20 |                         CharsetConverter(const std::string &from, const 
std::string &to) throw (Exception);
      |                                                                         
                 ^~~~~
make[3]: *** [Makefile:692: tests.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/<<PKGBUILDDIR>>/html'
make[2]: *** [Makefile:606: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:426: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j4 returned exit code 2
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: htmlcxx
Source-Version: 0.87-2
Done: Stephen Kitt <sk...@debian.org>

We believe that the bug you reported is fixed in the latest version of
htmlcxx, 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 984...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt <sk...@debian.org> (supplier of updated htmlcxx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 11 Oct 2021 13:28:13 +0200
Source: htmlcxx
Architecture: source
Version: 0.87-2
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon <cave...@debian.org>
Changed-By: Stephen Kitt <sk...@debian.org>
Closes: 984181
Changes:
 htmlcxx (0.87-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository.
 .
   [ Stephen Kitt ]
   * Drop unnecessary exception declarations. Closes: #984181.
   * Standards-Version 4.6.0, no change required.
Checksums-Sha1:
 c761cea91c821026f31fa486ecf01d9eb58d2ae1 2050 htmlcxx_0.87-2.dsc
 729f14075e2d5582f419f7f4f234251bd9af45f7 6664 htmlcxx_0.87-2.debian.tar.xz
 e44bb0ba5957076f3dd1d702e1eab4d2cdf65440 6335 htmlcxx_0.87-2_source.buildinfo
Checksums-Sha256:
 1d3f386abb34fbec36b11489cc09a595b931c3df0ea6935fafd9dc72cad227d4 2050 
htmlcxx_0.87-2.dsc
 39a539cb4beaf5e9eaa7ec1f8d162e02d809aefcd8bf93a1e9d91634b3a75fe2 6664 
htmlcxx_0.87-2.debian.tar.xz
 d7707620b81a024a74ce106dcf3c01f76a0c72b479f9fc120243a093da1def9d 6335 
htmlcxx_0.87-2_source.buildinfo
Files:
 e14b7d567668bcd7b21519da88dfcadd 2050 libs optional htmlcxx_0.87-2.dsc
 ada3aa764b43c3929b31a135213ad317 6664 libs optional 
htmlcxx_0.87-2.debian.tar.xz
 2a89b2c453a90e9c4dd14f66b1b2e3db 6335 libs optional 
htmlcxx_0.87-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmFkH9oACgkQgNMC9Yht
g5xqaA//auRhJ9RhikNFQwjlcd8cL0u1Z9vrtIETxrkxY9tCmlL3d7KoICE+mS9x
9xOmxAEDbWmkZUbJpOiH6/twwRyZOibPNaJxPEq3+wMKhTkfuVyMnlvqDVQZZIEi
ZdDOOhEj5GP5mV256Uz+N1MfZu2W89ILTzx27c1szy1n7Xjo28uHPpfQMiRKy5Cn
ZNtRWU1+Tq0Uo2CWOt/qsCVd3l4NnYxPLFHG5wegX9iaWGfZjMkYocmmmstfmf/f
5tYpOyQD+YrRRnoE3MW1DX1u32WdomzduqeOHNuMubVmT4OregKEdfn4rMqMTp2o
pl/QFooorIneFXHB1Ezp0LTAUdQCYPjhM75ayJ99xnTVr25AFTk3r3iGPTocIq3Y
Q4hPcoRsIwlm9e9t80Cff6J7TdeKMkLYQ4R9bEb2x5sJz9gpj2MHc8sg94bE4zYT
oJPTVot7izvfULw/imTMMArlFzfUQjjCTIrwnCBAXvZylw3CjjOcTPIeVP2n3SvS
XUC+/dNx5RcxcIAtfEoo9RuwsOkZQc8gR6ApTSKBsWv9BtVQ8qepRt0Ub/twaTRq
nbsPMi32ssne+mU3gUAgeT97cjkHUbaMbXj+aZPq/bazSy7QnjT6fQX9crVY/phg
NeR+b64v7RAdw3w0ZeA8IWQBbijFZCKrBxDEdBCfhV3r/FjuCtI=
=ctrI
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to