From: "Chen, Farrah" <farrah.chen@intel.com>
To: "edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>
Cc: "'wei.liu2@citrix.com'" <wei.liu2@citrix.com>,
"Hao, Xudong" <xudong.hao@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: OVMF compile error
Date: Wed, 14 Sep 2016 07:21:40 +0000 [thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC36D95F73@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: 1B925CC0CD9F3341B32D442251E7E1DC36D93C55@shsmsx102.ccr.corp.intel.com
Hi,
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.
Bisected and this error occurred from commit 8c8b6fb02342f7aa78e611a5f0f63dcf8fbf48f2.
commit 8c8b6fb02342f7aa78e611a5f0f63dcf8fbf48f2
Author: Wei Liu <wei.liu2@citrix.com<mailto:wei.liu2@citrix.com>>
Date: Tue Sep 6 12:54:47 2016 +0100
Config.mk: update OVMF commit
Signed-off-by: Wei Liu wei.liu2@citrix.com<mailto:wei.liu2@citrix.com>
We have updated OVMF to the latest master and cleaned everything before rebuilding.
Steps:
make clean
make xen -j8
./configure --enable-ovmf
make tools -j8
Then the error occurred.
.........................................................................................................................................................
make_tools.log:
......
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii:173: error: invalid combination of opcode and operands
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii:175: error: invalid combination of opcode and operands
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii:177: error: invalid combination of opcode and operands
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii:179: error: invalid combination of opcode and operands
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii:313: error: invalid combination of opcode and operands
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii:315: error: invalid combination of opcode and operands
make[7]: Leaving directory `/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib'
make[7]: *** [/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.obj] Error 1
build.py...
: error 7000: Failed to execute command
make tbuild [/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib]
build.py...
: error F002: Failed to build module
/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware/ovmf-dir-remote/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib.inf [X64, GCC44, DEBUG]
- Failed -
Best Regards,
Fan Chen
next parent reply other threads:[~2016-09-14 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1B925CC0CD9F3341B32D442251E7E1DC36D93C55@shsmsx102.ccr.corp.intel.com>
2016-09-14 7:21 ` Chen, Farrah [this message]
2017-07-06 8:36 OVMF compile error Chen, Farrah
2017-07-06 8:47 ` Laszlo Ersek
2017-07-07 2:12 ` Chen, Farrah
2017-08-11 2:46 ` Chen, Farrah
2017-08-11 11:21 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2018-11-07 4:39 Chen, Farrah
2018-11-07 5:37 ` yuchenlin
2018-11-07 10:00 ` 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-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=1B925CC0CD9F3341B32D442251E7E1DC36D95F73@shsmsx102.ccr.corp.intel.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