Mike -- I moved my !include StdLib.inc to the very end of EmulatorPkg.dsc and I found that the build issues went away. But if I included it before the [BuildOptions] line, it would have trouble with

Mike -- I don't have XCODE5 so I cant rebuild here but I can try out the WinHost.exe and I will check out the VS2017 and VS2015 changes since I have them handy. Tim

Hi Tim, I happened to be looking at this over the weekend. I was able to resolve the build issues for XCODE5 for the IA32 version of EmulatorPkg, but not X64. I did not verify if it boots yet, so

Can you try the way to append compiler option in [Components] section for the specific modules? I see StdLib/StdLib.inc has such usage.

I am having trouble building StdLib applications inside of EmulatorPkg.dsc. When I add !incude StdLib/StdLib.inc I will always see a warning message about stdio.h. This comes down to the use of /X

Hi Elena, hi Leif, I'll add the following comments: 1. Right now, the RPi3 firmware is set not to boot SD/USB by default, but boot into the UEFI Shell always. Therefore, if you want a

Tim: SVN sync is stop now (https://edk2.groups.io/g/devel/message/42917). And, BaseTools Binary support is also dropped (https://edk2.groups.io/g/devel/message/29436). So, you need to install

Liming -- I have done this (see log below). I deleted Conf and Build. A few things to note: I retrieved these using SVN (not GIT) and (as you can see below) I do not have Python

Please run edksetup with Reconfig to update local build_rule.txt. This requires to update nasm build rule. For example: edksetup.bat Reconfig Thanks Liming

Folks - I give up. If I do a clean install of EDK2 and put NASM in C:\Program Files\Nasm (in Windows) and do : set WORKSPACE=C:\Isi\Edk2Shell set NASM_PREFIX=C:\Program Files\Nasm edksetup

Hi Leif and Pete, My answers in blue. Best regards, Elena

Hi Elena, (+cc Pete) .efi indicated an application (or driver), as opposed to a script. My go-to test case is a standalone GRUB executable. Generated with grub-mkstandalone -O arm64-efi -o

Hello, I am using EDK2 https://github.com/tianocore/edk2 on a Raspberry PI 3B model. Installation went fine and I can access the UEFI Shell interface, where the commands work. But I’m now

Hi, Ard. I compared this output to my previous edk2 build (uses gcc 7.3) and noticed that the .eh_frame sections seem to be new with the gcc 8.3 compiler. I added -fno-exceptions and

You are missing the -fno-unwind-tables option. Please make sure that you apply commit cbf00651eda6818ca3c76115b8a18e3f6b23eef4 to your tree.

Hi, Ard. -bash-4.2$ readelf -S /x/edk2/Build/RELEASE_GCC5/AARCH64/MdeModulePkg/Universal/Network/DpcDxe/DpcDxe/DEBUG/DpcDxe.dll There are 25 section headers, starting at offset 0x2a940: Section

Could you dump the section headers of such a .dll using readelf -S please?

Your Conf/tools_def.txt is probably stale, and does not contain the -fno-pie option we added a while ago.

Here is a sample of the gcc command line: "/x/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc" -I/x/edk2/edk2/MlxPlatformPkg/Include -march=armv8-a+crc -g

Hello, Ard. The tools_def.txt was updated and both the -fno-pie and -fno-pic are specified when executing gcc. I don’t have access to the code at the moment but I will post the exact gcc command