From: Olaf Hering <olaf@aepfle.de>
To: "Chen, Farrah" <farrah.chen@intel.com>
Cc: "Hao, Xudong" <xudong.hao@intel.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: OVMF compile error
Date: Tue, 13 Sep 2016 19:12:12 +0200 [thread overview]
Message-ID: <20160913171212.GA27032@aepfle.de> (raw)
In-Reply-To: <20160913094101.GS15958@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 366 bytes --]
> > > On Mon, Sep 12, 2016 at 07:31:42AM +0000, Chen, Farrah wrote:
> > > > When I compile xen with the latest commit in RHEL 6.7, it failed when make tools. Errors showed when running edk2 build for OvmfPkgX64.
> > > > erAsm.iii:315: error: invalid combination of opcode and operands
The included nasm package is likely too old, 2.10.something is
required.
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-13 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1B925CC0CD9F3341B32D442251E7E1DC36D93C55@shsmsx102.ccr.corp.intel.com>
[not found] ` <20160912075301.GJ15958@citrix.com>
[not found] ` <1B925CC0CD9F3341B32D442251E7E1DC36D95741@shsmsx102.ccr.corp.intel.com>
[not found] ` <20160913093902.GO15958@citrix.com>
2016-09-13 9:41 ` OVMF compile error Wei Liu
2016-09-13 17:12 ` Olaf Hering [this message]
2016-09-14 1:59 ` Chen, Farrah
2016-09-14 10:02 ` Wei Liu
2016-09-14 2:00 ` Chen, Farrah
2016-09-14 2:00 ` Chen, Farrah
2016-09-14 2:21 ` Chen, Farrah
2016-09-14 7:07 ` Chen, Farrah
2016-09-14 7:21 ` 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-all 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=20160913171212.GA27032@aepfle.de \
--to=olaf@aepfle.de \
--cc=farrah.chen@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xudong.hao@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).