From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"sahajsarup@gmail.com" <sahajsarup@gmail.com>,
"canhkha26@gmail.com" <canhkha26@gmail.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Feng, Bob C" <bob.c.feng@intel.com>
Subject: Re: [edk2-devel] intel: EDK2 Build failure for Quark/Gallileo
Date: Fri, 28 Aug 2020 19:17:50 +0000 [thread overview]
Message-ID: <MN2PR11MB44610AB4CE24A4318F48AF1BD2520@MN2PR11MB4461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAGW0CY4-iv-SewrwjngkSvUdx0HjkGG_p3j+t8F2LUmp_m2YSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
Hi,
I have send a patch series for review that resolves the EDK2 Quark build failures.
https://edk2.groups.io/g/devel/message/64769
Please try this patch series and let me know if it resolves your issues.
There does appear to be a regression in BaseTools in the use of a RuleOverride in an
FDF file when the rule referenced is a complex rule with a GUIDed section. I have
removed the use of this feature in this patch series until the BaseTools issues is
investigated and resolved.
Thanks,
Mike
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Sahaj Sarup
Sent: Sunday, August 23, 2020 7:38 AM
To: devel@edk2.groups.io; canhkha26@gmail.com
Subject: Re: [edk2-devel] intel: EDK2 Build failure for Quark/Gallileo
Canh,
I've tried with both python 3 and 2 across ubuntu 18.04 and fedora 32.
On Sun, Aug 23, 2020, 19:45 Canh Kha <canhkha26@gmail.com<mailto:canhkha26@gmail.com>> wrote:
Sahaj,
Can you can with python 3.7.n or a newer one?
Thanks,
Canh Kha
[-- Attachment #2: Type: text/html, Size: 42647 bytes --]
prev parent reply other threads:[~2020-08-28 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 5:29 intel: EDK2 Build failure for Quark/Gallileo Sahaj Sarup
2020-08-22 19:00 ` [edk2-devel] " Andrew Fish
2020-08-23 14:15 ` Canh Kha
2020-08-23 14:38 ` Sahaj Sarup
2020-08-28 19:17 ` Michael D Kinney [this message]
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=MN2PR11MB44610AB4CE24A4318F48AF1BD2520@MN2PR11MB4461.namprd11.prod.outlook.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