[edk2-devel] OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40"

Thu May 9 06:37:28 UTC 2019

Sure, detailed log attached, no error in make_BaseTools.log, the error occurred in build edk2.
After running "build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5", error log is edk2_build.log.
After running "build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64", the error is different, error log is edk2_build_withoutGCC5.log.
Thanks a lot!

Thanks,
Fan

-----Original Message-----
From: Gao, Liming 
Sent: Thursday, May 9, 2019 2:25 PM
To: Chen, Farrah <farrah.chen at intel.com>; devel at edk2.groups.io; glin at suse.com
Cc: Hao, Xudong <xudong.hao at intel.com>; Wei, Danmei <danmei.wei at intel.com>; Feng, Bob C <bob.c.feng at intel.com>
Subject: RE: [edk2-devel] OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40"

Farrah:
  This is the problem in df7c81b5b219c9ae. Patch owner are looking it, then fix it. 

  On build failure, could you share more log? This log doesn't show what compiler error in the driver.

Thanks
Liming
> -----Original Message-----
> From: Chen, Farrah
> Sent: Thursday, May 9, 2019 2:19 PM
> To: Gao, Liming <liming.gao at intel.com>; devel at edk2.groups.io; 
> glin at suse.com
> Cc: Hao, Xudong <xudong.hao at intel.com>; Wei, Danmei 
> <danmei.wei at intel.com>
> Subject: RE: [edk2-devel] OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40"
> 
> Hi Liming,
> 
> 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 " 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 
> simplify
> 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/MdeModulePkg/Universal/
> ReportStatusCodeRouter/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=PlatformPeiStrings -m32 
> -march=i586 -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/Plat
> formPei/OUTPUT/./MemDetect.obj
> -I/home/fan/edk2/OvmfPkg/PlatformPei
> -I/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/OvmfPkg/PlatformPei/Pl
> atformPei/DEBUG -I/home/fan/edk2/IntelFrameworkModulePkg 
> -I/home/fan/edk2/IntelFrameworkModulePkg/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/home/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
> 
> build.py...
>  : error 7000: Failed to execute command
>         make tbuild
> [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/MdeModulePkg/Universal/
> StatusCodeHandler/Pei/StatusCodeHandlerPei]
> 
> build.py...
>  : error 7000: Failed to execute command
>         make tbuild 
> [/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/UefiCpuPkg/Universal/Ac
> pi/S3Resume2Pei/S3Resume2Pei]
> 
> 
> Thanks,
> Fan
> 
> -----Original Message-----
> From: Gao, Liming
> Sent: Thursday, May 9, 2019 11:35 AM
> To: devel at edk2.groups.io; Chen, Farrah <farrah.chen at intel.com>; 
> glin at suse.com
> Cc: Hao, Xudong <xudong.hao at intel.com>; Wei, Danmei 
> <danmei.wei at intel.com>
> Subject: RE: [edk2-devel] OVMF will not start to build using "OvmfPkg/build.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 at edk2.groups.io [mailto:devel at edk2.groups.io] On Behalf 
> > Of Chen, Farrah
> > Sent: Thursday, May 9, 2019 11:29 AM
> > To: devel at edk2.groups.io; glin at suse.com
> > Cc: Hao, Xudong <xudong.hao at intel.com>; Wei, Danmei 
> > <danmei.wei at intel.com>
> > 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 updated?
> >
> > [vmm at 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 at vmm-build edk2]$ echo $?
> > 1
> >
> >
> > Thanks,
> > Fan
> >
> >
> >
> > -----Original Message-----
> > From: devel at edk2.groups.io [mailto:devel at edk2.groups.io] On Behalf 
> > Of Gary Lin
> > Sent: Thursday, May 9, 2019 11:20 AM
> > To: devel at edk2.groups.io; Chen, Farrah <farrah.chen at intel.com>
> > Cc: Hao, Xudong <xudong.hao at intel.com>; Wei, Danmei 
> > <danmei.wei at intel.com>
> > 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 using "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 at 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 at 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
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > 

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#40280): https://edk2.groups.io/g/devel/message/40280
Mute This Topic: https://groups.io/mt/31551173/1813853
Group Owner: devel+owner at edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub  [edk2-devel-archive at redhat.com]
-=-=-=-=-=-=-=-=-=-=-=-

-------------- next part --------------
A non-text attachment was scrubbed...
Name: edk2_build.log
Type: application/octet-stream
Size: 8525 bytes
Desc: edk2_build.log
URL: <http://listman.redhat.com/archives/edk2-devel-archive/attachments/20190509/8b9f04cb/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make_BaseTools.log
Type: application/octet-stream
Size: 53316 bytes
Desc: make_BaseTools.log
URL: <http://listman.redhat.com/archives/edk2-devel-archive/attachments/20190509/8b9f04cb/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: edk2_build_withoutGCC5.log
Type: application/octet-stream
Size: 2712 bytes
Desc: edk2_build_withoutGCC5.log
URL: <http://listman.redhat.com/archives/edk2-devel-archive/attachments/20190509/8b9f04cb/attachment-0002.obj>