public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chen, Farrah" <farrah.chen@intel.com>
To: Gary Lin <glin@suse.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Hao, Xudong" <xudong.hao@intel.com>,
	"Wei, Danmei" <danmei.wei@intel.com>,
	"Gao, Liming" <liming.gao@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:04:42 +0000	[thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC3E2933C9@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190509040650.GC28997@GaryWorkstation>

Hi Gary,

Thanks a lot, we can build successfully with this method.
BTW, will this patch be merged to upstream?


Thanks,
Fan




-----Original Message-----
From: Gary Lin [mailto:glin@suse.com] 
Sent: Thursday, May 9, 2019 12:07 PM
To: Chen, Farrah <farrah.chen@intel.com>
Cc: devel@edk2.groups.io; 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 03:29:09AM +0000, Chen, Farrah wrote:
> Yes, thanks, my return value is 1.
> And how can we build ovmf correctlly? The build steps have been updated?
> 
You can tweak TestUtilModule() in edksetup.sh like this:

 function TestUtilModule()
 {
   if ( $PYTHON_COMMAND -c "import distutils.util" >/dev/null 2>&1 );then
-      return 1
+      return 0
   else
       echo Error: "No module named 'distutils.util"
-      return 0
+      return 1
   fi
 }

Cheers,

Gary Lin

> [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:04 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
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 [this message]
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=1B925CC0CD9F3341B32D442251E7E1DC3E2933C9@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