public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "Chen, Farrah" <farrah.chen@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"glin@suse.com" <glin@suse.com>
Cc: "Hao, Xudong" <xudong.hao@intel.com>,
	"Wei, Danmei" <danmei.wei@intel.com>,
	"Feng, Bob C" <bob.c.feng@intel.com>
Subject: Re: [edk2-devel] OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40"
Date: Thu, 9 May 2019 06:24:37 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E44584F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1B925CC0CD9F3341B32D442251E7E1DC3E2933E6@SHSMSX104.ccr.corp.intel.com>

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@intel.com>; devel@edk2.groups.io; glin@suse.com
> Cc: Hao, Xudong <xudong.hao@intel.com>; Wei, Danmei <danmei.wei@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/PlatformPei/OUTPUT/./MemDetect.obj
> -I/home/fan/edk2/OvmfPkg/PlatformPei
> -I/home/fan/edk2/Build/Ovmf3264/DEBUG_GCC5/IA32/OvmfPkg/PlatformPei/PlatformPei/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/Acpi/S3Resume2Pei/S3Resume2Pei]
> 
> 
> Thanks,
> Fan
> 
> -----Original Message-----
> From: Gao, Liming
> Sent: Thursday, May 9, 2019 11:35 AM
> To: devel@edk2.groups.io; Chen, Farrah <farrah.chen@intel.com>; glin@suse.com
> Cc: Hao, Xudong <xudong.hao@intel.com>; Wei, Danmei <danmei.wei@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@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 <xudong.hao@intel.com>; Wei, Danmei
> > <danmei.wei@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@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 <farrah.chen@intel.com>
> > Cc: Hao, Xudong <xudong.hao@intel.com>; Wei, Danmei
> > <danmei.wei@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@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
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > 


  reply	other threads:[~2019-05-09  6:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  2:31 OVMF will not start to build using "OvmfPkg/build.sh -a X64 -n 40" Chen, Farrah
2019-05-09  3:20 ` [edk2-devel] " Gary Lin
2019-05-09  3:29   ` Chen, Farrah
2019-05-09  3:35     ` Liming Gao
2019-05-09  6:19       ` Chen, Farrah
2019-05-09  6:24         ` Liming Gao [this message]
2019-05-09  6:37           ` Chen, Farrah
2019-05-09  6:42             ` Liming Gao
2019-05-09  6:54               ` Chen, Farrah
2019-05-09  4:06     ` Gary Lin
2019-05-09  6:04       ` Chen, Farrah
2019-05-09  6:20         ` Gary Lin
2019-05-09  6:25           ` Chen, Farrah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A89E2EF3DFEDB4C8BFDE51014F606A14E44584F@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox