Bug#976502: multiboot: FTBFS on arm64: gcc: error: unrecognized command-line option ‘-m32’

[Lucas Nussbaum]

Source: multiboot
Version: 0.6.96+20101113-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..  -m32 -nostdlib -fno-builtin -nostdinc -O -g -Wall -imacros ../config.h -Wdate-time  -DHAVE_CONFIG_H -I. -I..  -Wdate-time -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -specs=/usr/share/dpkg/no-pie-compile.specs -c -o kernel-boot.o `test -f 'boot.S' || echo './'`boot.S
> gcc: error: unrecognized command-line option ‘-m32’
> make[4]: *** [Makefile:430: kernel-boot.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/multiboot_0.6.96+20101113-2_unstable.log

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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.