Bug#1037913: marked as done (zytrax: ftbfs with GCC-13)
Your message dated Tue, 12 Sep 2023 09:22:14 +0000
with message-id <E1qfzb4-00CoVz-5R@fasolo.debian.org>
and subject line Bug#1037913: fixed in zytrax 0+git20201215-1.1
has caused the Debian Bug report #1037913,
regarding zytrax: ftbfs with GCC-13
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.)
--
1037913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037913
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:zytrax
Version: 0+git20201215-1
Severity: normal
Tags: sid trixie
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/zytrax_0+git20201215-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html
[...]
globals/base64.cpp:21:9: note: ‘uint8_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
globals/base64.cpp:22:16: error: expected ‘;’ before ‘char_array_4’
22 | uint8_t char_array_4[4];
| ^~~~~~~~~~~~~
| ;
globals/base64.cpp:25:17: error: ‘char_array_3’ was not declared in this scope
25 | char_array_3[i++] = *(buf++);
| ^~~~~~~~~~~~
globals/base64.cpp:25:39: error: ‘buf’ was not declared in this scope
25 | char_array_3[i++] = *(buf++);
| ^~~
globals/base64.cpp:27:25: error: ‘char_array_4’ was not declared in this scope
27 | char_array_4[0] = (char_array_3[0] & 0xfc) >> 2;
| ^~~~~~~~~~~~
globals/base64.cpp:40:25: error: ‘char_array_3’ was not declared in this scope
40 | char_array_3[j] = '\0';
| ^~~~~~~~~~~~
globals/base64.cpp:42:17: error: ‘char_array_4’ was not declared in this scope
42 | char_array_4[0] = (char_array_3[0] & 0xfc) >> 2;
| ^~~~~~~~~~~~
globals/base64.cpp:42:36: error: ‘char_array_3’ was not declared in this scope
42 | char_array_4[0] = (char_array_3[0] & 0xfc) >> 2;
| ^~~~~~~~~~~~
globals/base64.cpp: At global scope:
globals/base64.cpp:57:8: error: ‘uint8_t’ was not declared in this scope
57 | Vector<uint8_t> base64_decode(std::string const &encoded_string) {
| ^~~~~~~
globals/base64.cpp:57:8: note: ‘uint8_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
globals/base64.cpp:57:15: error: template argument 1 is invalid
57 | Vector<uint8_t> base64_decode(std::string const &encoded_string) {
| ^
globals/base64.cpp: In function ‘int base64_decode(const std::string&)’:
globals/base64.cpp:62:9: error: ‘uint8_t’ was not declared in this scope
62 | uint8_t char_array_4[4], char_array_3[3];
| ^~~~~~~
globals/base64.cpp:62:9: note: ‘uint8_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
globals/base64.cpp:65:69: error: ‘is_base64’ cannot be used as a function
65 | while (in_len-- && (encoded_string[in_] != '=') && is_base64(encoded_string[in_])) {
| ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
globals/base64.cpp:66:17: error: ‘char_array_4’ was not declared in this scope
66 | char_array_4[i++] = encoded_string[in_];
| ^~~~~~~~~~~~
globals/base64.cpp:72:25: error: ‘char_array_3’ was not declared in this scope
72 | char_array_3[0] = (char_array_4[0] << 2) + ((char_array_4[1] & 0x30) >> 4);
| ^~~~~~~~~~~~
globals/base64.cpp:77:37: error: request for member ‘push_back’ in ‘ret’, which is of non-class type ‘int’
77 | ret.push_back(char_array_3[i]);
| ^~~~~~~~~
globals/base64.cpp:84:25: error: ‘char_array_4’ was not declared in this scope
84 | char_array_4[j] = 0;
| ^~~~~~~~~~~~
globals/base64.cpp:87:25: error: ‘char_array_4’ was not declared in this scope
87 | char_array_4[j] = base64_chars.find(char_array_4[j]);
| ^~~~~~~~~~~~
globals/base64.cpp:89:17: error: ‘char_array_3’ was not declared in this scope
89 | char_array_3[0] = (char_array_4[0] << 2) + ((char_array_4[1] & 0x30) >> 4);
| ^~~~~~~~~~~~
globals/base64.cpp:89:36: error: ‘char_array_4’ was not declared in this scope
89 | char_array_3[0] = (char_array_4[0] << 2) + ((char_array_4[1] & 0x30) >> 4);
| ^~~~~~~~~~~~
globals/base64.cpp:94:29: error: request for member ‘push_back’ in ‘ret’, which is of non-class type ‘int’
94 | ret.push_back(char_array_3[j]);
| ^~~~~~~~~
scons: *** [globals/base64.o] Error 1
scons: building terminated because of errors.
make[1]: *** [Makefile:2: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:16: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: zytrax
Source-Version: 0+git20201215-1.1
Done: Marcos Talau <talau@debian.org>
We believe that the bug you reported is fixed in the latest version of
zytrax, 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 1037913@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marcos Talau <talau@debian.org> (supplier of updated zytrax 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: Sun, 10 Sep 2023 14:20:16 +0530
Source: zytrax
Architecture: source
Version: 0+git20201215-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Marcos Talau <talau@debian.org>
Closes: 1037913
Changes:
zytrax (0+git20201215-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/patches/01-fix_ftbfs_gcc-13.patch: New. Fix FTBFS with gcc-13.
Thanks to Adrian Bunk (Closes: #1037913).
Checksums-Sha1:
b7802fe98f86b8106e468aa8426a830687ba5be3 2041 zytrax_0+git20201215-1.1.dsc
74a471f5ad844fe56a0917280aaae27751188618 3620 zytrax_0+git20201215-1.1.debian.tar.xz
ae6beaecab0b756e13ac8322039764efca62614d 15825 zytrax_0+git20201215-1.1_source.buildinfo
Checksums-Sha256:
85039383f44984a50bc9da79ab97d3c9d7c9bcab03844ca607b27020c1eca3a6 2041 zytrax_0+git20201215-1.1.dsc
70fe1be6e890d2829e2a0de2ec5f1aa5cb84b8303c2c2d7fd09031dab39631e6 3620 zytrax_0+git20201215-1.1.debian.tar.xz
3d33be46feb9681d2479a0c71ac23713e1b9e5aad2002a764a6e763bc1fbb129 15825 zytrax_0+git20201215-1.1_source.buildinfo
Files:
f9bcf073a3d9cdada30882454608dbb3 2041 sound optional zytrax_0+git20201215-1.1.dsc
aaf83273df86652d7691e3bb9d205db3 3620 sound optional zytrax_0+git20201215-1.1.debian.tar.xz
9a65aa05e2da2084b04a5e653017d8e6 15825 sound optional zytrax_0+git20201215-1.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmT9hGgACgkQ9LqqgNso
ukwdqA/+Oh+m0UQyaGezZRPJyk0FXap3YjEQ2txxx4AeMxf4X5zXpYc80zKk9D/4
aMIJQma0/KRradiWwokYHYcdWzuNKJvWPBPdIBWg3QFOFoEi+wprG9wTOZoQdXdL
910HDN9cjmQ5rdLzLsJLjFLG65yFwdK864Xx0Hva5uEYx5R140p+5NZF4R2JwvU4
snsqHOGK2+90oQ4YXyZJRqcuEsOFx3MHOJcNiFtQNbOX4uEWoc43dszAMGt6U51i
MYeW+CZ4zute3B+VACG60rhKEN1ZgLCJybLOAghKuaenvKJkS+TvCipzp5EBLEdh
AUDpWjgBrG8MtRkEVYjsUNV8PcknI0aAwqI48bRY0DYZGJLf2zEwX5G9nnuc72KM
TYfVUfUXhR0+RvHrZHLoF+n4n1MbViZEWYxZGJC/0bjFhSRi9Vcwy5qGrYtvRoHq
kmyXB456P1P/tvj5y7m+TYfCGrgvC0YNXUufuybR6h5wbp+jbjm/NqyXml6O3qzk
UdTOZb+3Dw8ZF2+k8OxDj6axx/VKJotQfgDKc2kUlfWSAQCWfKoMaZm5Cg6ZEI0l
qXX4G+sY9loQUjMqvOhfxzyIMZYMFluXBS6dYIZ3SE7aOC9D0h6/iSA9dmtNeWzT
q9JeysllMp3GxUZNirrpqR3Na80ZPCJ/VZCmJCiM6WwNQMY12OY=
=25Z6
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: