From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.151, mailfrom: farrah.chen@intel.com) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by groups.io with SMTP; Wed, 08 May 2019 23:19:10 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2019 23:19:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,448,1549958400"; d="scan'208";a="169873356" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga002.fm.intel.com with ESMTP; 08 May 2019 23:19:10 -0700 Received: from shsmsx107.ccr.corp.intel.com (10.239.4.96) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 8 May 2019 23:19:09 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.33]) by SHSMSX107.ccr.corp.intel.com ([169.254.9.7]) with mapi id 14.03.0415.000; Thu, 9 May 2019 14:19:07 +0800 From: "Chen, Farrah" To: "Gao, Liming" , "devel@edk2.groups.io" , "glin@suse.com" CC: "Hao, Xudong" , "Wei, Danmei" Subject: Re: [edk2-devel] OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40" Thread-Topic: [edk2-devel] OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40" Thread-Index: AdUGDyS+XOvl88AuQFmC1Y1te2Ukkf//h+GA//94ScD//u7esP/9sxxw Date: Thu, 9 May 2019 06:19:06 +0000 Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC3E2933E6@SHSMSX104.ccr.corp.intel.com> References: <1B925CC0CD9F3341B32D442251E7E1DC3E2931EC@SHSMSX104.ccr.corp.intel.com> <20190509032023.GA28997@GaryWorkstation> <1B925CC0CD9F3341B32D442251E7E1DC3E2932BC@SHSMSX104.ccr.corp.intel.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4455FE@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4455FE@SHSMSX104.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOGFiZTFiZDItZDE2Mi00M2RiLTk0MGYtOWNmZjQ1MzQ0YWNhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiS2xROXNGNkJaNjRnbXRmVVY3bVQ0cVpzbWpOdHhhN0ZVelJxTVFKU3FJWjdid3dUVWs3akFVSENRU2NXbHRyaiJ9 x-ctpclassification: CTP_NT x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: farrah.chen@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Liming, We have been using " OvmfPkg/build.sh -a X64" for such a long time, ovmf c= an be built successfully with this method until commit df7c81b5b219c9ae, an= d in edk2/OvmfPkg/README, it asks me to use " OvmfPkg/build.sh". As Gray's advice, we modified return value of TestUtilModule() in edksetup= .sh, then it can succeed with " OvmfPkg/build.sh -a X64". And we met error with " build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64= -t GCC5" to build ovmf, fail log showed below. So, can we get a correct and official build method with no error? Thanks! edk2/OvmfPkg/README: 108 On systems with the bash shell you can use OvmfPkg/build.sh to simplif= y 109 building and running OVMF. 110 111 So, for example, to build + run OVMF X64: 112 $ OvmfPkg/build.sh -a X64 113 $ OvmfPkg/build.sh -a X64 qemu 114 115 And to run a 64-bit UEFI bootable ISO image: 116 $ OvmfPkg/build.sh -a X64 qemu -cdrom /path/to/disk-image.iso 117 118 To build a 32-bit OVMF without debug messages using GCC 4.8: 119 $ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC48 Fail log: build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 .......... build.py... : error 7000: Failed to execute command make tbuild [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/MdeModu= lePkg/Universal/ReportStatusCodeRouter/Pei/ReportStatusCodeRouterPei] "gcc" -g -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -Wn= o-array-bounds -ffunction-sections -fdata-sections -include AutoGen.h -fno-= common -DSTRING_ARRAY_NAME=3DPlatformPeiStrings -m32 -march=3Di586 -malign-= double -fno-stack-protector -D EFI32 -fno-asynchronous-unwind-tables -Wno-a= ddress -fno-pic -fno-pie -flto -Os -mno-mmx -mno-sse -D DISABLE_NEW_DEPRECA= TED_INTERFACES -c -o /home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/OvmfPkg/= PlatformPei/PlatformPei/OUTPUT/./MemDetect.obj -I/home/fan/edk2/OvmfPkg/Pla= tformPei -I/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/OvmfPkg/PlatformPe= i/PlatformPei/DEBUG -I/home/fan/edk2/IntelFrameworkModulePkg -I/home/fan/ed= k2/IntelFrameworkModulePkg/Include -I/home/fan/edk2/MdePkg -I/home/fan/edk2= /MdePkg/Include -I/home/fan/edk2/MdePkg/Include/Ia32 -I/home/fan/edk2/MdeMo= dulePkg -I/home/fan/edk2/MdeModulePkg/Include -I/home/fan/edk2/SecurityPkg = -I/home/fan/edk2/SecurityPkg/Include -I/home/fan/edk2/UefiCpuPkg -I/home/fa= n/edk2/UefiCpuPkg/Include -I/home/fan/edk2/OvmfPkg -I/home/fan/edk2/OvmfPkg= /Include /home/fan/edk2/OvmfPkg/PlatformPei/MemDetect.c build.py... : error 7000: Failed to execute command make tbuild [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/MdeModu= lePkg/Universal/StatusCodeHandler/Pei/StatusCodeHandlerPei] build.py... : error 7000: Failed to execute command make tbuild [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/UefiCpu= Pkg/Universal/Acpi/S3Resume2Pei/S3Resume2Pei] Thanks, Fan -----Original Message----- From: Gao, Liming=20 Sent: Thursday, May 9, 2019 11:35 AM To: devel@edk2.groups.io; Chen, Farrah ; glin@suse.= com Cc: Hao, Xudong ; Wei, Danmei Subject: RE: [edk2-devel] OVMF will not start to build using "OvmfPkg/buil= d.sh -a X64 -n 40" Fan: The below is my step to build OvmfIa32X64. I don't try OvmfPkg/build.sh 1. . edksetup.sh 2. cd BaseTools, type make 3. cd .. 4. build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 Thanks Liming > -----Original Message----- > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of=20 > Chen, Farrah > Sent: Thursday, May 9, 2019 11:29 AM > To: devel@edk2.groups.io; glin@suse.com > Cc: Hao, Xudong ; Wei, Danmei=20 > > Subject: Re: [edk2-devel] OVMF will not start to build using "OvmfPkg/bu= ild.sh -a X64 -n 40" >=20 > Yes, thanks, my return value is 1. > And how can we build ovmf correctlly? The build steps have been updated? >=20 > [vmm@vmm-build edk2]$ OvmfPkg/build.sh -a X64 -n 40 Initializing=20 > workspace /home/fan/edk2/BaseTools Loading previous configuration from= =20 > /home/fan/edk2/Conf/BuildEnv.sh > WORKSPACE: /home/fan/edk2 > EDK_TOOLS_PATH: /home/fan/edk2/BaseTools > CONF_PATH: /home/fan/edk2/Conf > [vmm@vmm-build edk2]$ echo $? > 1 >=20 >=20 > Thanks, > Fan >=20 >=20 >=20 > -----Original Message----- > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of=20 > Gary Lin > Sent: Thursday, May 9, 2019 11:20 AM > To: devel@edk2.groups.io; Chen, Farrah > Cc: Hao, Xudong ; Wei, Danmei=20 > > Subject: Re: [edk2-devel] OVMF will not start to build using "OvmfPkg/bu= ild.sh -a X64 -n 40" >=20 > On Thu, May 09, 2019 at 02:31:13AM +0000, Chen, Farrah wrote: > > Hi, > > > > We build the latest OVMF and found that it doesn't start to build usin= g "OvmfPkg/build.sh -a X64 -n 40" actually. > > > > Step: > > git clone https://github.com/tianocore/edk2.git > > cd edk2 > > git submodule init > > git submodule update -recursive > > OvmfPkg/build.sh -a X64 -n 40 > > Then it didn't start to build. > > > > log: > > [vmm@vmm-build edk2]$ OvmfPkg/build.sh -a X64 -n 40 Initializing=20 > > workspace /home/fan/edk2/BaseTools Loading previous configuration=20 > > from /home/fan/edk2/Conf/BuildEnv.sh > > WORKSPACE: /home/fan/edk2 > > EDK_TOOLS_PATH: /home/fan/edk2/BaseTools > > CONF_PATH: /home/fan/edk2/Conf > > [vmm@vmm-build edk2]$ > > > > We use the latest commit: 792f0d4f12ad5c01afdf9c92df8c479ff0f19a79,=20 > > and we found the first commit has such issue is > df7c81b5b219c9aee776baa466dd64c9d318dd80. > > Do you have any advice? > > > TestUtilModule() returned the opposite value. > For the shell, 0 for good, and 1 for bad. >=20 > Gary Lin >=20 > > > > Thanks, > > Fan > > > > > > > > > > >=20 >=20 >=20 >=20 >=20