Your message dated Wed, 03 Mar 2021 17:29:19 +0100
with message-id <[email protected]>
and subject line Re: Bug#983997: bochs: ftbfs with GCC-11
has caused the Debian Bug report #983997,
regarding bochs: 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 [email protected]
immediately.)
--
983997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983997
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:bochs
Version: 2.6.11+dfsg-4
Severity: normal
Tags: sid bookworm
User: [email protected]
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/bochs_2.6.11+dfsg-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.
[...]
architecture: amd64
essential: true
-
package: autotools-dev
version: 20180224.1+nmu1
architecture: all
-
package: autopoint
version: 0.21-4
architecture: all
-
package: automake
version: 1:1.16.3-2
architecture: all
-
package: autoconf
version: 2.69-14
architecture: all
-
package: adwaita-icon-theme
version: 3.38.0-1
architecture: all
-
package: adduser
version: 3.118
architecture: all
-
package: acpica-tools
version: 20200925-1.2
architecture: amd64
background-packages: 61989
foreground-packages: 1
total-packages: 61990
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: bochs_2.6.11+dfsg-4
Machine Architecture: amd64
Package: bochs
Package-Time: 0
Source-Version: 2.6.11+dfsg-4
Space: n/a
Status: given-back
Version: 2.6.11+dfsg-4
--------------------------------------------------------------------------------
Finished at 2021-03-01T20:45:25Z
Build needed 00:00:00, no disk space
E: Package build dependencies not satisfied; skipping
DC-Status: Failed 70.367808813s
DC-Time-Estimation: 70.367808813 versus expected 276 (r/m: 2.9222480372162845 ;
m: 70.367808813)
--- End Message ---
--- Begin Message ---
Hi Matthias,
Your test didn’t actually test whether bochs builds with GCC-11, in this
case:
The following packages have unmet dependencies:
gcc-i686-linux-gnu : Depends: cpp-i686-linux-gnu (= 4:11-20210116-1)
but it is not going to be installed
Depends: gcc-11-i686-linux-gnu (>= 11-20210116-0~)
but it is not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Regards,
Stephen
Le 03/03/2021 17:10, Matthias Klose a écrit :
Package: src:bochs
Version: 2.6.11+dfsg-4
Severity: normal
Tags: sid bookworm
User: [email protected]
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/bochs_2.6.11+dfsg-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.
[...]
architecture: amd64
essential: true
-
package: autotools-dev
version: 20180224.1+nmu1
architecture: all
-
package: autopoint
version: 0.21-4
architecture: all
-
package: automake
version: 1:1.16.3-2
architecture: all
-
package: autoconf
version: 2.69-14
architecture: all
-
package: adwaita-icon-theme
version: 3.38.0-1
architecture: all
-
package: adduser
version: 3.118
architecture: all
-
package: acpica-tools
version: 20200925-1.2
architecture: amd64
background-packages: 61989
foreground-packages: 1
total-packages: 61990
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: bochs_2.6.11+dfsg-4
Machine Architecture: amd64
Package: bochs
Package-Time: 0
Source-Version: 2.6.11+dfsg-4
Space: n/a
Status: given-back
Version: 2.6.11+dfsg-4
--------------------------------------------------------------------------------
Finished at 2021-03-01T20:45:25Z
Build needed 00:00:00, no disk space
E: Package build dependencies not satisfied; skipping
DC-Status: Failed 70.367808813s
DC-Time-Estimation: 70.367808813 versus expected 276 (r/m:
2.9222480372162845 ; m: 70.367808813)
--- End Message ---
