Source: edk2
Version: 2020.08-1
Severity: important
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.

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint'
> "gcc" -MMD -MF 
> /<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/DriverEntryPoint.obj.deps
>  -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror 
> -Wno-array-bounds -include AutoGen.h -fno-common -ffunction-sections 
> -fdata-sections -fno-stack-protector 
> -DSTRING_ARRAY_NAME=UefiDriverEntryPointStrings -m64 -fno-stack-protector 
> "-DEFIAPI=__attribute__((ms_abi))" -maccumulate-outgoing-args -mno-red-zone 
> -Wno-address -mcmodel=small -fpie -fno-asynchronous-unwind-tables 
> -Wno-address -flto -DUSING_LTO -Os -Wno-unused-but-set-variable 
> -Wno-unused-const-variable -DMDEPKG_NDEBUG -mno-mmx -mno-sse -D 
> DISABLE_NEW_DEPRECATED_INTERFACES -c -o 
> /<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/./DriverEntryPoint.obj
>  -I/<<PKGBUILDDIR>>/MdePkg/Library/UefiDriverEntryPoint 
> -I/<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/DEBUG
>  -I/<<PKGBUILDDIR>>/MdePkg -I/<<PKGBUILDDIR>>/MdePkg/Include 
> -I/<<PKGBUILDDIR>>/MdePkg/Test/UnitTest/Include 
> -I/<<PKGBUILDDIR>>/MdePkg/Include/X64 
> /<<PKGBUILDDIR>>/MdePkg/Library/UefiDriverEntryPoint/DriverEntryPoint.c
> gcc: error: unrecognized command-line option ‘-m64’
> make[2]: Entering directory 
> '/<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiLib/UefiLib'
> "gcc" -MMD -MF 
> /<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiLib/UefiLib/OUTPUT/Acpi.obj.deps
>  -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror 
> -Wno-array-bounds -include AutoGen.h -fno-common -ffunction-sections 
> -fdata-sections -fno-stack-protector -DSTRING_ARRAY_NAME=UefiLibStrings -m64 
> -fno-stack-protector "-DEFIAPI=__attribute__((ms_abi))" 
> -maccumulate-outgoing-args -mno-red-zone -Wno-address -mcmodel=small -fpie 
> -fno-asynchronous-unwind-tables -Wno-address -flto -DUSING_LTO -Os 
> -Wno-unused-but-set-variable -Wno-unused-const-variable -DMDEPKG_NDEBUG 
> -mno-mmx -mno-sse -D DISABLE_NEW_DEPRECATED_INTERFACES -c -o 
> /<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiLib/UefiLib/OUTPUT/./Acpi.obj
>  -I/<<PKGBUILDDIR>>/MdePkg/Library/UefiLib 
> -I/<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiLib/UefiLib/DEBUG
>  -I/<<PKGBUILDDIR>>/MdePkg -I/<<PKGBUILDDIR>>/MdePkg/Include 
> -I/<<PKGBUILDDIR>>/MdePkg/Test/UnitTest/Include 
> -I/<<PKGBUILDDIR>>/MdePkg/Include/X64 
> /<<PKGBUILDDIR>>/MdePkg/Library/UefiLib/Acpi.c
> gcc: error: unrecognized command-line option ‘-m64’
> Building ... 
> /<<PKGBUILDDIR>>/MdeModulePkg/Library/DxeReportStatusCodeLib/DxeReportStatusCodeLib.inf
>  [X64]
> gcc: error: unrecognized command-line option ‘-maccumulate-outgoing-args’
> gcc: error: unrecognized command-line option ‘-mno-red-zone’
> gcc: error: unrecognized command-line option ‘-mno-mmx’
> gcc: error: unrecognized command-line option ‘-mno-sse’; did you mean 
> ‘-fno-dse’?
> make[2]: *** [GNUmakefile:300: 
> /<<PKGBUILDDIR>>/Build/OvmfX64/RELEASE_GCC5/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/DriverEntryPoint.obj]
>  Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/edk2_2020.08-1_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.

Reply via email to