I see the issue: We're not passing -fno-stack-protector to AARCH64 GCC toolchains (although arguably we should just enable support for it...). Can you try hacking up your tools_def to add -fno-stack-protector to GCC_AARCH64_CC_FLAGS? It should fix your build issues. On Sat, Aug 20, 2022 at 2:51 AM Rebecca Cran wrote: > I'm using gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) on Ubuntu > 20.04.4, from the Ubuntu repo. > > I'm building it with: > > > export PACKAGES_PATH=$PWD/edk2:$PWD/edk2-platforms:$PWD/edk2-non-osi > export WORKSPACE=$PWD > export GCC5_AARCH64_PREFIX=aarch64-linux-gnu- > > . ./edk2/edksetup.sh > build -p ./Features/Ext4Pkg/Ext4Pkg.dsc -a AARCH64 -b RELEASE -t GCC5 > > > Some of the messages are: > > > "aarch64-linux-gnu-gcc" -o > /home/bcran/src/beaglebone/Build/Ext4Pkg/RELEASE_GCC5/AARCH64/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe/DEBUG/Ext4Dxe.dll > -Wl,--emit-relocs -nostdlib -Wl,--gc-sections -u _ModuleEntryPoint > -Wl,-e,_ModuleEntryPoint,-Map,/home/bcran/src/beaglebone/Build/Ext4Pkg/RELEASE_GCC5/AARCH64/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe/DEBUG/Ext4Dxe.map > -z common-page-size=0x20 -z common-page-size=0x1000 -flto -Os > -L/home/bcran/src/beaglebone/edk2/ArmPkg/Library/GccLto -llto-aarch64 > -Wl,-plugin-opt=-pass-through=-llto-aarch64 -Wno-lto-type-mismatch > -Wl,--start-group,@/home/bcran/src/beaglebone/Build/Ext4Pkg/RELEASE_GCC5/AARCH64/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe/OUTPUT/static_library_files.lst,--end-group > -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror > -Wno-array-bounds -include AutoGen.h -fno-common -ffunction-sections > -fdata-sections -DSTRING_ARRAY_NAME=Ext4DxeStrings -g -Os -fshort-wchar > -fno-builtin -fno-strict-aliasing -Wall -Werror -Wno-array-bounds -include > AutoGen.h -fno-common -mlittle-endian -fno-short-enums -fverbose-asm > -funsigned-char -ffunction-sections -fdata-sections -Wno-address > -fno-asynchronous-unwind-tables -fno-unwind-tables -fno-pic -fno-pie > -ffixed-x18 -mcmodel=small -flto -Wno-unused-but-set-variable > -Wno-unused-const-variable -D DISABLE_NEW_DEPRECATED_INTERFACES > -Wl,--script=/home/bcran/src/beaglebone/edk2/BaseTools/Scripts/GccBase.lds > -Wl,--defsym=PECOFF_HEADER_SIZE=0x228 -Wno-error > /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: > /tmp/Ext4Dxe.dll.sETaOX.ltrans0.ltrans.o: in function > `InternalAllocatePool.constprop.0': > /home/bcran/src/beaglebone/edk2/MdePkg/Library/UefiMemoryAllocationLib/MemoryAllocationLib.c:368: > undefined reference to `__stack_chk_guard' > /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: > /tmp/Ext4Dxe.dll.sETaOX.ltrans0.ltrans.o: relocation > R_AARCH64_ADR_PREL_PG_HI21 against symbol `__stack_chk_guard' which may > bind externally can not be used when making a shared object; recompile with > -fPIC > /home/bcran/src/beaglebone/edk2/MdePkg/Library/UefiMemoryAllocationLib/MemoryAllocationLib.c:368:(.text.InternalAllocatePool.constprop.0+0xc): > dangerous relocation: unsupported relocation > /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: > /home/bcran/src/beaglebone/edk2/MdePkg/Library/UefiMemoryAllocationLib/MemoryAllocationLib.c:368: > undefined reference to `__stack_chk_guard' > /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: > /home/bcran/src/beaglebone/edk2/MdePkg/Library/UefiMemoryAllocationLib/MemoryAllocationLib.c:382: > undefined reference to `__stack_chk_fail' > /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: > /tmp/Ext4Dxe.dll.sETaOX.ltrans0.ltrans.o: in function > `OrderedCollectionInsert.constprop.0': > /home/bcran/src/beaglebone/edk2/MdePkg/Library/BaseOrderedCollectionRedBlackTreeLib/BaseOrderedCollectionRedBlackTreeLib.c:584: > undefined reference to `__stack_chk_guard' > > -- > Rebecca Cran > > > On 8/19/22 18:46, Pedro Falcato wrote: > > Hi Rebecca, > > What EDK2 toolchain are you using? And how is your toolchain configured > (or where did you get it from?)? It seems that it's trying to use the stack > protector automatically... > > Thanks, > Pedro > > > On Sat, 20 Aug 2022, 00:40 Rebecca Cran, wrote: > >> ./Features/Ext4Pkg/Ext4Pkg.dsc is also failing - with errors about >> __stack_chk_guard and __stack_chk_fail. >> >> >> And I get an error from Andy Hayes' email: "Your message couldn't be >> delivered to the recipient because you don't have permission to send to it." >> >> >> -- >> Rebecca Cran >> >> >> On 8/19/22 17:35, Rebecca Cran wrote: >> >> I have an armplatbld.sh script that goes through and tries to build as >> many of the Arm (AARCH64 and ARM) platforms in edk2-platforms as possible. >> >> I'm think this used to work for these, but I'm getting some errors now. >> >> I'm using edk2-platforms 46686eeb7e78efe603badd86f13777d9fb070fb8 and >> edk2 e2ac68a23b4954d5c0399913a1df3dd9fd90315d. >> >> >> Drivers/ASIX/Asix.dsc (fails with undefined references to __stack_chk_guard >> and __stack_chk_fail) >> >> Drivers/DisplayLink/DisplayLinkPkg/DisplayLinkPkg.dsc (fails with >> undefined references to __stack_chk_guard and __stack_chk_fail) >> Platform/Socionext/DeveloperBox/DeveloperBoxMm.dsc (fails with bad >> definition for symbol '_GLOBAL_OFFSET_TABLE_'@0x72d8 or unsupported >> symbol type. For example, absolute and undefined symbols are not >> supported.) >> >> Drivers/StandaloneMmCpu/StandaloneMmCpu (fails with undefined references >> to __stack_chk_guard and __stack_chk_fail) >> Platform/StandaloneMm/PlatformStandaloneMmPkg/PlatformStandaloneMmRpmb.dsc >> (fails with bad definition for symbol '_GLOBAL_OFFSET_TABLE_'@0x72d8 or >> unsupported symbol type. For example, absolute and undefined symbols are >> not supported.) >> >> >> -- >> Rebecca Cran >> >> >> -- Pedro Falcato