On 22 March 2016 at 13:57, James Bottomley <[email protected]> wrote: > On Tue, 2016-03-22 at 13:38 +0100, Ard Biesheuvel wrote: >> On 22 March 2016 at 13:35, James Bottomley >> <[email protected]> wrote: >> > On Tue, 2016-03-22 at 13:01 +0100, Ard Biesheuvel wrote: >> > > On 22 March 2016 at 04:25, Gao, Liming <[email protected]> >> > > wrote: >> > > > Reviewed-by: Liming Gao <[email protected]> >> > > > >> > > >> > > This patch breaks the AARCH64 build: >> > > >> > > Processing meta-data .... >> > > >> > > build.py... >> > > : error F000: Not supported macro is found in make command : >> > > $(ARCHCC_FLAGS) $(PLATFORM_FLAGS) -g -fshort-wchar >> > > -fno-strict-aliasing -Wall -Werror -Wno-array-bounds >> > > -ffunction-sections -fdata-sections -c -include AutoGen.h -fno >> > > -common >> > > -DSTRING_ARRAY_NAME=DxePcdLibStrings -mcmodel=tiny -g -Os >> > > -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-array >> > > -bounds -c >> > > -include AutoGen.h -fno-common -mlittle-endian -fno-short-enums >> > > -save-temps -fverbose-asm -fsigned-char -ffunction-sections >> > > -fdata-sections -fomit-frame-pointer -fno-builtin -Wno-address >> > > -fno-asynchronous-unwind-tables -O0 >> > > [/home/ard/build/uefi >> > > -next/MdePkg/Library/DxePcdLib/DxePcdLib.inf] >> > > >> > > >> > > Could we *please* start testing BaseTools changes on other >> > > toolchains/platforms than X64/VS? >> > >> > Since edk2 is Intel centric, this is how I do it: >> > >> > http://blog.hansenpartnership.com/constructing-architecture-emulati >> > on-containers/ >> > >> > As long as you're running an OS which supports containers (i.e. >> > Linux >> > not Windows), you can bring up a native aarch64 (or arm 32 bit) >> > build >> > environment for edk2 on an x86 system. >> > >> >> Thanks for the link, it looks interesting. However, there is no need >> at all to build natively. In fact, you don't even need the aarch64 >> toolchain to find out that the aarch64 build is broken by this patch, >> since it errors out way before even invoking the compiler. > > Well, it depends what you do. I'm not really looking to find build > errors, I need to validate a runtime system (so boot the output in qemu > and run it through its paces). Since the build service I use builds > natively, I also need to test the native build (cross compilers don't > always work the same way the native build does). >
Oh, I absolutely agree that building natively is preferred over cross-building, and I should probably consider migrating my own CI build jobs against EDK2 to a native environment (which wasn't available when I first got involved with UEFI) My point was simply that this particular patch breaks the build way before it even matters whether you build natively, cross build or even have no compatible toolchain installed to begin with. _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
