From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"afish@apple.com" <afish@apple.com>,
"lersek@redhat.com" <lersek@redhat.com>
Cc: "wanweiyang@uniontech.com" <wanweiyang@uniontech.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Chen, Christine" <yuwei.chen@intel.com>
Subject: Re: [edk2-devel] 你好我来寻求帮助 Hello, I'm here for help
Date: Mon, 10 Aug 2020 02:20:53 +0000 [thread overview]
Message-ID: <CY4PR11MB1526D50470EB6A779E9BDD8D80440@CY4PR11MB1526.namprd11.prod.outlook.com> (raw)
In-Reply-To: <C80E7AB4-88B1-4CBB-A665-B18E414239D7@apple.com>
The problem may be in the source directory "edk2-2020.05". Please don't use '.' in the directory name. You can try the directory name with "edk2_202005".
Thanks
Liming
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Andrew Fish via groups.io
Sent: 2020年8月8日 1:30
To: devel@edk2.groups.io; lersek@redhat.com
Cc: wanweiyang@uniontech.com
Subject: Re: [edk2-devel] 你好我来寻求帮助 Hello, I'm here for help
> On Aug 7, 2020, at 10:10 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>
> Hi,
>
> On 08/07/20 05:06, 弯威仰 wrote:
>
>> Hello, I have this problem in compiling ovmf, as shown in the figure
>> below. Do you have any good solutions to it?
>
> The problem doesn't seem particularly related to OVMF. I suggest
> filing a bug at <https://bugzilla.tianocore.org/>, and pasting the
> Python stack dump as text (not as an image).
>
Also a Python “KeyError:” means something was missing in a dictionary so this could just be bad error handling in Python and something else broke. Thus please attach the the output for the entire build to the BZ.
Thanks,
Andrew Fish
> Thanks
> Laszlo
>
>
>
>
prev parent reply other threads:[~2020-08-10 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 3:06 你好我来寻求帮助 Hello, I'm here for help 弯威仰
2020-08-07 17:10 ` [edk2-devel] " Laszlo Ersek
2020-08-07 17:29 ` Andrew Fish
2020-08-10 2:20 ` Liming Gao [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=CY4PR11MB1526D50470EB6A779E9BDD8D80440@CY4PR11MB1526.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