Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

[Lucas Nussbaum]

On 20/04/24 at 15:39 +0300, Michael Tokarev wrote:
> 20.04.2024 15:33, Lucas Nussbaum wrote:
> [..]
> > This is part of a mass rebuild, first building on arm64 and then on
> > armhf and armel. So I'm not suggesting anything. :-)
> 
> Aha.
> 
> > Is this failing because the build is trying to build arch:all packages,
> > that can only be built on amd64? If so, the bug severity could be
> > lowered, clearly.
> 
> Well.  Yes, this is exactly the case.  qemu uses quite a few cross-compilers 
> to
> build various firmware components.  This is arch-all package qemu-system-data.
> Most of these cross-compilers are available on x86 _only_, including the
> mentioned gcc-powerpc64-linux-gnu.
> 
> I especially made these deps to be in Build-Depends-Indep only, - to be able
> to (re)build qemu on non-x86 by using `apt --arch-only`.
> 
> I can't say this is a bug to begin with, - wrt lowering its severity.  If it
> is a bug, it's a bug in gcc, not qemu (since it is gcc which does not provide
> these cross-compilers on all architectures).  Or in the build environment.

Sure. The only reason for leaving a bug behind is that, if there had
been a "FTBFS everywhere except amd64 when building arch-indep
packages", I would have caught this and not filed this bug. wishlist +
wontfix would be OK.

Lucas

Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

[Michael Tokarev]

20.04.2024 15:33, Lucas Nussbaum wrote:
[..]

This is part of a mass rebuild, first building on arm64 and then on
armhf and armel. So I'm not suggesting anything. :-)


Aha.


Is this failing because the build is trying to build arch:all packages,
that can only be built on amd64? If so, the bug severity could be
lowered, clearly.


Well.  Yes, this is exactly the case.  qemu uses quite a few cross-compilers to
build various firmware components.  This is arch-all package qemu-system-data.
Most of these cross-compilers are available on x86 _only_, including the
mentioned gcc-powerpc64-linux-gnu.

I especially made these deps to be in Build-Depends-Indep only, - to be able
to (re)build qemu on non-x86 by using `apt --arch-only`.

I can't say this is a bug to begin with, - wrt lowering its severity.  If it
is a bug, it's a bug in gcc, not qemu (since it is gcc which does not provide
these cross-compilers on all architectures).  Or in the build environment.

Thanks,

/mjt

Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

[Lucas Nussbaum]

On 20/04/24 at 15:27 +0300, Michael Tokarev wrote:
> Control: tag -1 + moreinfo
> Control: found -1 1:4.2-2
> 
> 20.04.2024 15:11, Lucas Nussbaum wrote:
> > Source: qemu
> > Version: 1:8.2.2+ds-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: trixie sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
> 
> 
> > >   sbuild-build-depends-main-dummy : Depends: gcc-powerpc64-linux-gnu but 
> > > it is not installable
> > > E: Unable to correct problems, you have held broken packages.
> 
> I don't understand what are you suggesting to do here.

Hi Michael,

This is part of a mass rebuild, first building on arm64 and then on
armhf and armel. So I'm not suggesting anything. :-)

Is this failing because the build is trying to build arch:all packages,
that can only be built on amd64? If so, the bug severity could be
lowered, clearly.

Lucas

Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

[Michael Tokarev]

Control: tag -1 + moreinfo
Control: found -1 1:4.2-2

20.04.2024 15:11, Lucas Nussbaum wrote:

Source: qemu
Version: 1:8.2.2+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64




  sbuild-build-depends-main-dummy : Depends: gcc-powerpc64-linux-gnu but it is 
not installable
E: Unable to correct problems, you have held broken packages.


I don't understand what are you suggesting to do here.

Should I disable all foreign compilers and code in qemu?  This way,
qemu will be nearly useless.

Or should you perhaps file a bug against gcc to provide powerpc64 
cross-compilers
for arm64?  If it's this variant, why are you filing this bug report against 
qemu?

Thanks,

/mjt

Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

[Lucas Nussbaum]

Source: qemu
Version: 1:8.2.2+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), python3:any, python3-venv, 
> python3:any (>> 3.11) | python3-tomli, meson (>> 0.63.0~), ninja-build, flex, 
> bison, python3-sphinx, python3-sphinx-rtd-theme, build-essential, fakeroot, 
> libglib2.0-dev, zlib1g-dev, libcapstone-dev, libaio-dev, libjack-dev, 
> libpulse-dev, libasound2-dev, libpipewire-0.3-dev (>> 0.3.60), libbpf-dev, 
> libbrlapi-dev, libcap-ng-dev, libcurl4-gnutls-dev, libfdt-dev, libfuse3-dev, 
> gnutls-dev, libgtk-3-dev, libvte-2.91-dev, libiscsi-dev, libncurses-dev, 
> libvirglrenderer-dev, libepoxy-dev, libdrm-dev, libgbm-dev, libnfs-dev, 
> libnuma-dev, libcacard-dev, libpixman-1-dev, librbd-dev, libglusterfs-dev, 
> libsasl2-dev, libsdl2-dev, libseccomp-dev, libslirp-dev, libspice-server-dev, 
> librdmacm-dev, libibverbs-dev, libibumad-dev, liburing-dev, libusb-1.0-0-dev, 
> libusbredirparser-dev, libssh-dev, libzstd-dev, libvdeplug-dev, nettle-dev, 
> libudev-dev, libjpeg-dev, libpng-dev, libpmem-dev, gcc-i686-linux-gnu, 
> device-tree-compiler, gcc-s390x-linux-gnu, gcc-alpha-linux-gnu, 
> gcc-powerpc-linux-gnu, gcc-powerpc64-linux-gnu, libssl-dev, 
> gcc-sparc64-linux-gnu, fcode-utils, xsltproc, gcc-hppa-linux-gnu, 
> gcc-riscv64-linux-gnu, gcc-arm-none-eabi
> Merged Build-Conflicts: oss4-dev
> Filtered Build-Depends: debhelper-compat (= 13), python3:any, python3-venv, 
> python3:any (>> 3.11), meson (>> 0.63.0~), ninja-build, flex, bison, 
> python3-sphinx, python3-sphinx-rtd-theme, build-essential, fakeroot, 
> libglib2.0-dev, zlib1g-dev, libcapstone-dev, libaio-dev, libjack-dev, 
> libpulse-dev, libasound2-dev, libpipewire-0.3-dev (>> 0.3.60), libbpf-dev, 
> libbrlapi-dev, libcap-ng-dev, libcurl4-gnutls-dev, libfdt-dev, libfuse3-dev, 
> gnutls-dev, libgtk-3-dev, libvte-2.91-dev, libiscsi-dev, libncurses-dev, 
> libvirglrenderer-dev, libepoxy-dev, libdrm-dev, libgbm-dev, libnfs-dev, 
> libnuma-dev, libcacard-dev, libpixman-1-dev, librbd-dev, libglusterfs-dev, 
> libsasl2-dev, libsdl2-dev, libseccomp-dev, libslirp-dev, libspice-server-dev, 
> librdmacm-dev, libibverbs-dev, libibumad-dev, liburing-dev, libusb-1.0-0-dev, 
> libusbredirparser-dev, libssh-dev, libzstd-dev, libvdeplug-dev, nettle-dev, 
> libudev-dev, libjpeg-dev, libpng-dev, libpmem-dev, gcc-i686-linux-gnu, 
> device-tree-compiler, gcc-s390x-linux-gnu, gcc-alpha-linux-gnu, 
> gcc-powerpc-linux-gnu, gcc-powerpc64-linux-gnu, libssl-dev, 
> gcc-sparc64-linux-gnu, fcode-utils, xsltproc, gcc-hppa-linux-gnu, 
> gcc-riscv64-linux-gnu, gcc-arm-none-eabi
> Filtered Build-Conflicts: oss4-dev
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [3845 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1785 B]
> Fetched 6245 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: gcc-powerpc64-linux-gnu but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/qemu_8.2.2+ds-2_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See