Source: edk2 Severity: normal Once the default gcc becomes gcc-11, edk2 will begin to FTBFS:
"arm-linux-gnueabihf-gcc" -MMD -MF /<<PKGBUILDDIR>>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/Arm/ashldi3.obj.deps -mthumb -march=armv7-a -E -x assembler-with-cpp -include AutoGen.h -DOPENSBI_EXTERNAL_SBI_TYPES=OpensbiTypes.h -I/<<PKGBUILDDIR>>/ArmPkg/Library/CompilerIntrinsicsLib/Arm -I/<<PKGBUILDDIR>>/ArmPkg/Library/CompilerIntrinsicsLib -I/<<PKGBUILDDIR>>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/DEBUG -I/<<PKGBUILDDIR>>/MdePkg -I/<<PKGBUILDDIR>>/MdePkg/Include -I/<<PKGBUILDDIR>>/MdePkg/Test/UnitTest/Include -I/<<PKGBUILDDIR>>/MdePkg/Include/Arm -I/<<PKGBUILDDIR>>/ArmPkg -I/<<PKGBUILDDIR>>/ArmPkg/Include /<<PKGBUILDDIR>>/ArmPkg/Library/CompilerIntrinsicsLib/Arm/ashldi3.S > /<<PKGBUILDDIR>>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/Arm/ashldi3.ii cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU I'm guessing - but haven't tested - that this is fallout from the following change in gcc-11: gcc-11 (11.1.0-2) experimental; urgency=medium [...] * For armhf configure --with-arch=<arch>+fp, dropping the --with-fpu= option. [...] -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
