From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2603:3026:480::10; helo=muon.bluestop.org; envelope-from=rebecca@bluestop.org; receiver=edk2-devel@lists.01.org Received: from muon.bluestop.org (muon.bluestop.org [IPv6:2603:3026:480::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1E06321CB74A4 for ; Thu, 10 May 2018 08:44:58 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 99EB687037; Thu, 10 May 2018 09:44:59 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id WDYuM4VKmqG8; Thu, 10 May 2018 09:44:58 -0600 (MDT) Received: from [10.86.58.77] (rap-us.hgst.com [199.255.44.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 10 May 2018 09:44:58 -0600 (MDT) To: "Gao, Liming" , Laszlo Ersek , "apianti@aol.com" Cc: "edk2-devel@lists.01.org" References: <1634a4575fc-1dd7-e1c8@webjas-vae180.srv.aolmail.net> <463855a2-2b5b-a636-fab7-59e82bae80a5@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E227DA4@SHSMSX104.ccr.corp.intel.com> From: Rebecca Cran Message-ID: Date: Thu, 10 May 2018 09:44:55 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E227DA4@SHSMSX104.ccr.corp.intel.com> Subject: Re: Trying to build OVMF fails X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 15:44:59 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US I've had to update the toolchain definitions in edk2\Conf in the past to point WINSDK to a newer version, since I've been using VS2015 for a few years now. The error about not finding "C:\Program" is from the build tool not being able to find rc.exe, likely because you don't have the Windows SDK version 8.0 installed. -- Rebecca On 5/10/2018 9:06 AM, Gao, Liming wrote: > VS build requires to install WINSDK. VS2013 requires WINSDK8. This path c:\Program Files (x86)\Windows Kits\8.0\bin\x64\rc.exe is from the installed WINSDK8. > When you installs visual studio, you can select winsdk and install it together VS compiler. > >> -----Original Message----- >> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek >> Sent: Thursday, May 10, 2018 10:43 PM >> To: apianti@aol.com >> Cc: edk2-devel@lists.01.org >> Subject: Re: [edk2] Trying to build OVMF fails >> >> On 05/10/18 15:37, apianti@aol.com wrote: >>> I am having a problem building OVMF to use as firmware for QEMU to test EFI binaries. I can only build the X64 arch of OVMF in linux. >> In windows both IA32, IA32/X64, and X64 all fail with some variation of this error: >>> >>> >>> >>> >>> "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\x86_amd64\cl.exe" >> /Fod:\development\edk2\Build\OvmfX64\RELEASE_VS2013x86\X64\MdeModulePkg\Bus\Pci\EhciDxe\EhciDxe\OUTPUT\.\EhciUrb.obj >> /nologo /c /WX /GS- /W4 /Gs32768 /D UNICODE /O1b2s /GL /Gy /FIAutoGen.h /EHs-c- /GR- /GF /Gw /D MDEPKG_NDEBUG /D >> DISABLE_NEW_DEPRECATED_INTERFACES /Id:\development\edk2\MdeModulePkg\Bus\Pci\EhciDxe >> /Id:\development\edk2\Build\OvmfX64\RELEASE_VS2013x86\X64\MdeModulePkg\Bus\Pci\EhciDxe\EhciDxe\DEBUG >> /Id:\development\edk2\MdePkg /Id:\development\edk2\MdePkg\Include /Id:\development\edk2\MdePkg\Include\X64 >> /Id:\development\edk2\MdeModulePkg /Id:\development\edk2\MdeModulePkg\Include >> d:\development\edk2\MdeModulePkg\Bus\Pci\EhciDxe\EhciUrb.c >>> 'c:\Program' is not recognized as an internal or external command, >>> operable program or batch file. >>> NMAKE : fatal error U1077: '"c:\Program Files (x86)\Windows Kits\8.0\bin\x64\rc.exe' : return code '0x1' >>> Stop. >> Sorry, I can't comment on the VS toolchains (I don't use them). >> >>> And in linux IA32 and IA32/X64 fail with some varation of this error: >>> >>> >>> >>> "GenFw" -e DXE_DRIVER -o >> /home/development/Desktop/edk2/Build/OvmfIa32/RELEASE_GCC5/IA32/MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultTole >> rantWriteDxe/DEBUG/FaultTolerantWriteDxe.efi >> /home/development/Desktop/edk2/Build/OvmfIa32/RELEASE_GCC5/IA32/MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultTole >> rantWriteDxe/DEBUG/FaultTolerantWriteDxe.dll >>> GenFw: ERROR 3000: Invalid >>> >> /home/development/Desktop/edk2/Build/OvmfIa32/RELEASE_GCC5/IA32/MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultTole >> rantWriteDxe/DEBUG/FaultTolerantWriteDxe.dll unsupported ELF EM_386 relocation 0xa. >>> GenFw: ERROR 3000: Invalid >>> >> /home/development/Desktop/edk2/Build/OvmfIa32/RELEASE_GCC5/IA32/MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultTole >> rantWriteDxe/DEBUG/FaultTolerantWriteDxe.dll unsupported ELF EM_386 relocation 0x9. >> >> Interesting; what gcc version are you using with the GCC5 toolchain? >> I've just built OVMF like this: >> >> $ build \ >> -a IA32 \ >> -p OvmfPkg/OvmfPkgIa32.dsc \ >> -D SMM_REQUIRE \ >> -D SECURE_BOOT_ENABLE \ >> -t GCC5 \ >> -n 4 \ >> -b RELEASE \ >> -D HTTP_BOOT_ENABLE \ >> --cmd-len=65536 \ >> --hash >> >> with an up-to-date Fedora 28 install: >> - gcc (GCC) 8.1.1 20180502 (Red Hat 8.1.1-1) >> - binutils-2.29.1-23.fc28.x86_64 >> >>> How can I get the IA32 build working? Also I see ARM and AARCH64 OVMF images in packages, how are these being built? I get that >> the architectures are unsupported. >> >> Do you mean that "distro packages are unsupported by upstream edk2"? >> Edk2 does support ARM and AARCH64. >> >> It is true that the OvmfPkg DSC files target only IA32, IA32X64, and >> X64, but the ArmVirtPkg DSC files target ARM and AARCH64 QEMU and Xen >> virtual machines. You can build ArmVirtPkg platforms with >> cross-compilers from x86_64, or natively on AARCH64 at the least (I've >> never tried native building on ARM). >> >> Thanks >> Laszlo >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel