Your message dated Fri, 2 Aug 2024 21:55:11 +0300
with message-id <6f19607c-09b3-482a-93a0-0832744e8...@tls.msk.ru>
and subject line Re: Bug#1075428: qemu: ftbfs with GCC-14
has caused the Debian Bug report #1075428,
regarding qemu: ftbfs with GCC-14
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.)
--
1075428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qemu
Version: 1:8.2.5+ds-2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/qemu_8.2.5+ds-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html
[...]
architecture: amd64
essential: true
-
package: autotools-dev
version: 20220109.1
architecture: all
-
package: autopoint
version: 0.22.5-1
architecture: all
-
package: automake
version: 1:1.16.5-1.3
architecture: all
-
package: autoconf
version: 2.71-3
architecture: all
-
package: at-spi2-common
version: 2.50.0-1
architecture: all
-
package: adwaita-icon-theme
version: 46.0-1
architecture: all
-
package: adduser
version: 3.137
architecture: all
background-packages: 76200
foreground-packages: 1
total-packages: 76201
broken-packages: 0
+------------------------------------------------------------------------------+
| Cleanup |
+------------------------------------------------------------------------------+
Purging /<<BUILDDIR>>
Not cleaning session: cloned chroot in use
E: Package build dependencies not satisfied; skipping
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
Build Architecture: amd64
Build Type: binary
Build-Space: n/a
Build-Time: 0
Distribution: unstable
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: qemu_1:8.2.5+ds-2
Machine Architecture: amd64
Package: qemu
Package-Time: 0
Source-Version: 1:8.2.5+ds-2
Space: n/a
Status: given-back
Version: 1:8.2.5+ds-2
--------------------------------------------------------------------------------
Finished at 2024-07-02T00:08:45Z
Build needed 00:00:00, no disk space
E: Package build dependencies not satisfied; skipping
DC-Status: Failed 42.9666076s
DC-Time-Estimation: 42.9666076 versus expected 4160 (r/m: 95.81937281918434 ;
m: 42.9666076)
--- End Message ---
--- Begin Message ---
On Thu, 4 Jul 2024 14:21:07 +0300 Michael Tokarev <m...@tls.msk.ru> wrote:
Control: tag -1 + unreproducible
I tried to reproduce this one, but I can't.
Created a buildd sid chroot with mmdebstrap, added experimental main sources,
installed gcc and g++, and used this chroot with sbuild to build current qemu.
It builds just fine, installing everything which is needed, - including all
cross
compilers.
I can only guess there was a temporary error during python3-defaults change,
when
not all python3-related packages used in qemu build process has been (re)built
with python3.12. Or something like that.
In other words, no something gcc- or qemu-related.
One more month has passed, there's no additional info available, and as I
wrote the last time, I see no issues with qemu building with gcc-14.
Closing this bug report now. If you think this is incorrect, please
feel free to re-open this bug report.
Thanks,
/mjt
--- End Message ---
