From: "Chen, Farrah" <farrah.chen@intel.com>
To: Olaf Hering <olaf@aepfle.de>
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: Wed, 14 Sep 2016 01:59:49 +0000 [thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC36D95DA5@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20160913171212.GA27032@aepfle.de>
Hi
We can try the latest nasm. But there is still a problem that the included nasm package does not work, it works well before xen commit (8c8b6fb02) . Does RHEL 6.7 still support compiling xen now?
Thanks,
Fan Chen
-----Original Message-----
From: Olaf Hering [mailto:olaf@aepfle.de]
Sent: Wednesday, September 14, 2016 1:12 AM
To: Chen, Farrah <farrah.chen@intel.com>
Cc: Wei Liu <wei.liu2@citrix.com>; Hao, Xudong <xudong.hao@intel.com>; xen-devel@lists.xen.org
Subject: Re: [Xen-devel] OVMF compile error
> > > 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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-14 1:59 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
2016-09-14 1:59 ` Chen, Farrah [this message]
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=1B925CC0CD9F3341B32D442251E7E1DC36D95DA5@shsmsx102.ccr.corp.intel.com \
--to=farrah.chen@intel.com \
--cc=olaf@aepfle.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.