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.115, mailfrom: liming.gao@intel.com) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by groups.io with SMTP; Wed, 08 May 2019 23:24:38 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2019 23:24:38 -0700 X-ExtLoop1: 1 Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga006.fm.intel.com with ESMTP; 08 May 2019 23:24:38 -0700 Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 8 May 2019 23:24:37 -0700 Received: from shsmsx153.ccr.corp.intel.com (10.239.6.53) by fmsmsx111.amr.corp.intel.com (10.18.116.5) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 8 May 2019 23:24:37 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.33]) by SHSMSX153.ccr.corp.intel.com ([169.254.12.150]) with mapi id 14.03.0415.000; Thu, 9 May 2019 14:24:37 +0800 From: "Liming Gao" To: "Chen, Farrah" , "devel@edk2.groups.io" , "glin@suse.com" CC: "Hao, Xudong" , "Wei, Danmei" , "Feng, Bob C" 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//thGMA= Date: Thu, 9 May 2019 06:24:37 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E44584F@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> <1B925CC0CD9F3341B32D442251E7E1DC3E2933E6@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <1B925CC0CD9F3341B32D442251E7E1DC3E2933E6@SHSMSX104.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOGFiZTFiZDItZDE2Mi00M2RiLTk0MGYtOWNmZjQ1MzQ0YWNhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiS2xROXNGNkJaNjRnbXRmVVY3bVQ0cVpzbWpOdHhhN0ZVelJxTVFKU3FJWjdid3dUVWs3akFVSENRU2NXbHRyaiJ9 dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: liming.gao@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Farrah: This is the problem in df7c81b5b219c9ae. Patch owner are looking it, the= n fix it.=20 On build failure, could you share more log? This log doesn't show what c= ompiler error in the driver. Thanks Liming > -----Original Message----- > From: Chen, Farrah > Sent: Thursday, May 9, 2019 2:19 PM > 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/bu= ild.sh -a X64 -n 40" >=20 > Hi Liming, >=20 > We have been using " OvmfPkg/build.sh -a X64" for such a long time, ovmf= can be built successfully with this method until commit > df7c81b5b219c9ae, and in edk2/OvmfPkg/README, it asks me to use " OvmfPk= g/build.sh". > As Gray's advice, we modified return value of TestUtilModule() in edkset= up.sh, then it can succeed with " OvmfPkg/build.sh -a X64". > And we met error with " build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X= 64 -t GCC5" to build ovmf, fail log showed below. > So, can we get a correct and official build method with no error? > Thanks! >=20 > edk2/OvmfPkg/README: > 108 On systems with the bash shell you can use OvmfPkg/build.sh to simpl= ify > 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 >=20 >=20 > Fail log: > build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 > .......... >=20 > build.py... > : error 7000: Failed to execute command > make tbuild > [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/MdeModulePkg/Universal/Re= portStatusCodeRouter/Pei/ReportStatusCodeRouter > Pei] > "gcc" -g -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -= Wno-array-bounds -ffunction-sections -fdata-sections -include > AutoGen.h -fno-common -DSTRING_ARRAY_NAME=3DPlatformPeiStrings -m32 -mar= ch=3Di586 -malign-double -fno-stack-protector -D EFI32 > -fno-asynchronous-unwind-tables -Wno-address -fno-pic -fno-pie -flto -Os= -mno-mmx -mno-sse -D > DISABLE_NEW_DEPRECATED_INTERFACES -c -o > /home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/OvmfPkg/PlatformPei/Platfo= rmPei/OUTPUT/./MemDetect.obj > -I/home/fan/edk2/OvmfPkg/PlatformPei > -I/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/OvmfPkg/PlatformPei/Plat= formPei/DEBUG > -I/home/fan/edk2/IntelFrameworkModulePkg -I/home/fan/edk2/IntelFramework= ModulePkg/Include -I/home/fan/edk2/MdePkg > -I/home/fan/edk2/MdePkg/Include -I/home/fan/edk2/MdePkg/Include/Ia32 -I/= home/fan/edk2/MdeModulePkg > -I/home/fan/edk2/MdeModulePkg/Include -I/home/fan/edk2/SecurityPkg -I/ho= me/fan/edk2/SecurityPkg/Include > -I/home/fan/edk2/UefiCpuPkg -I/home/fan/edk2/UefiCpuPkg/Include -I/home/= fan/edk2/OvmfPkg -I/home/fan/edk2/OvmfPkg/Include > /home/fan/edk2/OvmfPkg/PlatformPei/MemDetect.c >=20 > build.py... > : error 7000: Failed to execute command > make tbuild > [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/MdeModulePkg/Universal/St= atusCodeHandler/Pei/StatusCodeHandlerPei] >=20 > build.py... > : error 7000: Failed to execute command > make tbuild [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/UefiC= puPkg/Universal/Acpi/S3Resume2Pei/S3Resume2Pei] >=20 >=20 > Thanks, > Fan >=20 > -----Original Message----- > From: Gao, Liming > Sent: Thursday, May 9, 2019 11:35 AM > To: devel@edk2.groups.io; Chen, Farrah ; glin@sus= e.com > Cc: Hao, Xudong ; Wei, Danmei > Subject: RE: [edk2-devel] OVMF will not start to build using "OvmfPkg/bu= ild.sh -a X64 -n 40" >=20 > Fan: > The below is my step to build OvmfIa32X64. I don't try OvmfPkg/build.s= h >=20 > 1. . edksetup.sh > 2. cd BaseTools, type make > 3. cd .. > 4. build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 >=20 > Thanks > Liming > > -----Original Message----- > > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of > > Chen, Farrah > > Sent: Thursday, May 9, 2019 11:29 AM > > To: 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" > > > > Yes, thanks, my return value is 1. > > And how can we build ovmf correctlly? The build steps have been update= d? > > > > [vmm@vmm-build edk2]$ OvmfPkg/build.sh -a X64 -n 40 Initializing > > workspace /home/fan/edk2/BaseTools Loading previous configuration 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]$ echo $? > > 1 > > > > > > Thanks, > > Fan > > > > > > > > -----Original Message----- > > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of > > Gary Lin > > Sent: Thursday, May 9, 2019 11:20 AM > > To: devel@edk2.groups.io; Chen, Farrah > > Cc: Hao, Xudong ; Wei, Danmei > > > > Subject: Re: [edk2-devel] OVMF will not start to build using "OvmfPkg/= build.sh -a X64 -n 40" > > > > 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 us= ing "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 > > > workspace /home/fan/edk2/BaseTools Loading previous configuration > > > 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, > > > 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. > > > > Gary Lin > > > > > > > > Thanks, > > > Fan > > > > > > > > > > > > > > > > > > > > > > > > >=20