public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wang, Fei1" <fei1.wang@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Lin, Wenson" <wenson.lin@intel.com>,
	"Chai, George" <george.chai@intel.com>,
	"Liu, Shijie" <shijie.liu@intel.com>,
	"Deng, Bob" <bob.deng@intel.com>,
	"Wang, Fei1" <fei1.wang@intel.com>
Subject: CR WhitleyRp BIOS build failure
Date: Mon, 30 Sep 2019 08:00:29 +0000	[thread overview]
Message-ID: <DD426BBCA2424D4495CBF2726304CCCB52744CE4@SHSMSX103.ccr.corp.intel.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]

Hi,

I am working on a BIOS sighting, which need to build SKX/ICX BIOS to test.
Build commands:
  WhitleyRpPkg\PlatformBIOSBuild.py -c SKX -b RELEASE -t VS15
  WhitleyRpPkg\PlatformBIOSBuild.py -c ICX -b RELEASE -t VS15

But the build tool always reports an unknow fatal error while processing a certain driver.
And it asks me to send email to devel@edk2.groups.io for help.
The attachment are 3 build logs for your reference.

Note:
When I first encountered this issue, I tried several times of clean build, but not work.
Then I created a new workdirectory and downloaded a new source code, it is able to build pass for 1st time, after that met the unknow fatal error as well in the following builds.
I tried to re-download a new source code, but the failure happened starting from the 1st build.
Command to download source code: edkrepo clone . DCG10nm

Till now, I am still stuck in the build issue, please help to take a look at this issue since it blocks our debug activity.

Thanks,
Fei


[-- Attachment #1.2: Type: text/html, Size: 3739 bytes --]

[-- Attachment #2: WhitleyRp_BIOS_Build_Logs.zip --]
[-- Type: application/x-zip-compressed, Size: 340706 bytes --]

             reply	other threads:[~2019-09-30  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30  8:00 Wang, Fei1 [this message]
2019-09-30 21:46 ` [edk2-devel] CR WhitleyRp BIOS build failure Andrew Fish

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=DD426BBCA2424D4495CBF2726304CCCB52744CE4@SHSMSX103.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