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

Bug#984180: marked as done (htdig: ftbfs with GCC-11)



Your message dated Mon, 29 Nov 2021 18:48:48 +0000
with message-id <E1mrlho-0008bR-LP@fasolo.debian.org>
and subject line Bug#984180: fixed in htdig 1:3.2.0b6-19
has caused the Debian Bug report #984180,
regarding htdig: 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 owner@bugs.debian.org
immediately.)


-- 
984180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984180
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:htdig
Version: 1:3.2.0b6-18
Severity: normal
Tags: sid bookworm
User: debian-gcc@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 ‘<type error>’ 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 '/<<PKGBUILDDIR>>/htword'
make[1]: *** [Makefile:451: all-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:20: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: htdig
Source-Version: 1:3.2.0b6-19
Done: Andreas Henriksson <andreas@fatal.se>

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

Debian distribution maintenance software
pp.
Andreas Henriksson <andreas@fatal.se> (supplier of updated htdig 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 29 Nov 2021 19:27:04 +0100
Source: htdig
Architecture: source
Version: 1:3.2.0b6-19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Henriksson <andreas@fatal.se>
Closes: 984180
Changes:
 htdig (1:3.2.0b6-19) unstable; urgency=medium
 .
   * QA Upload.
   * Add debian/patches/gcc-11 by Slávek Banko (Closes: #984180)
Checksums-Sha1:
 ddc32536c6016f4844b3c2cc432c7624ecc6dfb6 1769 htdig_3.2.0b6-19.dsc
 22d97df53f7526faab6dbbdfd26e718b2d5e2517 42240 htdig_3.2.0b6-19.debian.tar.xz
 039a2777ec5e07cca2293692a67ed1714c8e5b68 6334 htdig_3.2.0b6-19_amd64.buildinfo
Checksums-Sha256:
 24bdd7ac8e0f8bacfca315d2fdb5706292872494ceb2cc1696e682323c2b85f4 1769 htdig_3.2.0b6-19.dsc
 a866c19aaa658c66efc27022c743a6dec1b33db40b75fee6e5efe62a271b6bea 42240 htdig_3.2.0b6-19.debian.tar.xz
 eb0ea100f7ab38d4641ccf2273d3a7db04bbe06848f00870cb678812a32264ce 6334 htdig_3.2.0b6-19_amd64.buildinfo
Files:
 c522939b22ca859d916fdd6986383bc7 1769 web optional htdig_3.2.0b6-19.dsc
 007159b0bd343f33440574f280aece68 42240 web optional htdig_3.2.0b6-19.debian.tar.xz
 0758bbbf29469d687b3241fb005dcb2c 6334 web optional htdig_3.2.0b6-19_amd64.buildinfo

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

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAmGlHhkRHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwaN4g//QM6EF9+91OPiuFemhTAficzgBFNApXYb
I7QZ4jQcXhj9pNviyMn0HvT1v6YcsDR4+DQK+IK60+u0sQV/d+PEWfCxjATO8dAa
wyYD8hnxA09wrQ0LkEyR6PD4TH1ZInWyyFsxrMqfXj1eMpf2L4HeXTp+SJCSqZMI
pohjvblt/0JR0emMkyMtiy6AI8hRF7bQlF4/v4QQEALfiBgdaJYpNLTq6gJwPRTp
9TqzF0q0DlDuKZdXGqidZLgauSrd/DlezXK9wuwfXjVdF2JhfK8eQfvW7wQDMKEu
Ev8O3Ik0MemOL6w1NV3bvYWZhAbV9niO7JEiuhk8HQL4J4uO+XS9Fanrnl75iOpD
+V+5LWPz3YGw/W04Vu6UyEIQjpaPeF72FmkPnHbpS8uE/li9iFoM+AOXqd0SbKt2
HCtVVM06sjKLETI/pXgC9XvLSJoMMEdyAfa2H4cyTL9nm7rHnQJWCOHrKri750iF
qzcGbKFrnlIx2L513Vnp2JAE+yJErXR8y8hFjbFe2aBHnNj5MA1Wkq/bw0sZM4yF
cOiC9gtEXPBlwAnGFk0BI9lGDZcZdF7m/NXEh+EKXC0fmtsLvlwxB6oswtp7GryW
N7srrkEUg+ciPrKbmP4nkMG3qqt+vXcX36Nnp698M+oxnnBOgfjI1DuwJBJYq6D9
r1krBbL9yAw=
=4tnR
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: