From: Sudeep Holla <sudeep.holla@arm.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
"edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@lists.01.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: Build failure with latest edk2/tianocore tip
Date: Wed, 19 Oct 2016 14:38:44 +0100 [thread overview]
Message-ID: <e74c1318-0e71-c26d-c4bd-9e7085447f88@arm.com> (raw)
In-Reply-To: <B9726D6DCCFB8B4CA276A9169B02216D4F3AEC5D@SHSMSX103.ccr.corp.intel.com>
On 19/10/16 14:34, Zhu, Yonghong wrote:
> Thanks . Actually I also need to file a bug on Bugzilla for
> BaseTools to enhance the error message to be more clear. It should
> not report such Traceback error.
>
That would be great. I didn't expect e6 in the error message to be part
of the array in that .dec file. It was only after you pointed ou, I
could relate that. Thanks again.
--
Regards,
Sudeep
prev parent reply other threads:[~2016-10-19 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 10:06 Build failure with latest edk2/tianocore tip Sudeep Holla
2016-10-19 11:41 ` Zhu, Yonghong
2016-10-19 12:52 ` Zhu, Yonghong
2016-10-19 13:16 ` Sudeep Holla
2016-10-19 13:34 ` Zhu, Yonghong
2016-10-19 13:38 ` Sudeep Holla [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=e74c1318-0e71-c26d-c4bd-9e7085447f88@arm.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