Your message dated Thu, 25 Jul 2024 22:36:02 -0700
with message-id <87r0bgvhod.fsf@wireframe>
and subject line Re: Bug#1075593: u-boot: ftbfs with GCC-14
has caused the Debian Bug report #1075593,
regarding u-boot: 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.)
--
1075593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:u-boot
Version: 2024.01+dfsg-5
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/u-boot_2024.01+dfsg-5_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
[...]
package: bash
version: 5.2.21-2.1
architecture: amd64
essential: true
-
package: base-passwd
version: 3.6.4
architecture: amd64
essential: true
-
package: base-files
version: 13.3
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
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: u-boot_2024.01+dfsg-5
Machine Architecture: amd64
Package: u-boot
Package-Time: 0
Source-Version: 2024.01+dfsg-5
Space: n/a
Status: given-back
Version: 2024.01+dfsg-5
--------------------------------------------------------------------------------
Finished at 2024-07-02T00:52:32Z
Build needed 00:00:00, no disk space
E: Package build dependencies not satisfied; skipping
DC-Status: Failed 38.855714336s
DC-Time-Estimation: 38.855714336 versus expected 268 (r/m: 5.897312392264959 ;
m: 38.855714336)
--- End Message ---
--- Begin Message ---
Control: notfound 1075593 2024.01+dfsg-5
On 2024-07-03, Vagrant Cascadian wrote:
> Control: tag 1075593 moreinfo
>
> On 2024-07-03, Matthias Klose wrote:
>> The full build log can be found at:
>> http://qa-logs.debian.net/2024/07/01/u-boot_2024.01+dfsg-5_unstable_gccexp.log
>> The last lines of the build log are at the end of this report.
>
> Seems like the build dependencies failed to install; The more
> interesting part of the build log is:
>
> The following packages have unmet dependencies:
> gcc-14-aarch64-linux-gnu : Depends: libgcc-14-dev-arm64-cross (>=
> 14-20240207-1cross1) but 14-20240127-1cross1 is to be installed
> gcc-14-arm-linux-gnueabihf : Depends: libgcc-14-dev-armhf-cross (>=
> 14-20240207-1cross1) but 14-20240127-1cross1 is to be installed
> gcc-14-i686-linux-gnu : Depends: libgcc-14-dev-i386-cross (>=
> 14-20240207-1cross1) but 14-20240127-1cross1 is to be installed
> gcc-14-riscv64-linux-gnu : Depends: libgcc-14-dev-riscv64-cross (>=
> 14-20240207-1cross1) but 14-20240127-1cross1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.
> E: Package installation failed
> Not removing build depends: cloned chroot in use
>
> I do not think the problem is u-boot here, but solely the fact that
> u-boot depends on cross-toolchains which were not yet available?
>
> Please re-run the tests when the cross-toolchains become available.
Builds fine now that installable gcc-14 cross-toolchains have landed in
sid. Marking as done.
live well,
vagrant
signature.asc
Description: PGP signature
--- End Message ---
