From: "Chen, Farrah" <farrah.chen@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"'edk2-devel@ml01.01.org'" <edk2-devel@ml01.01.org>
Cc: "'xen-devel@lists.xen.org'" <xen-devel@lists.xen.org>,
Olaf Hering <olaf@aepfle.de>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>
Subject: Re: edk2 compile error
Date: Tue, 20 Sep 2016 07:19:01 +0000 [thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC36E24CB5@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <7a819c6f-42ed-f7b7-bd4f-8b98f8cb67b8@redhat.com>
Hi All,
Thank you. I installed nasm-2.12.02 and it workd. We will upgrade to RHEL-7 soon.
Thanks
Fan Chen
-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Monday, September 19, 2016 7:00 PM
To: Chen, Farrah <farrah.chen@intel.com>; 'edk2-devel@ml01.01.org' <edk2-devel@ml01.01.org>
Cc: 'xen-devel@lists.xen.org' <xen-devel@lists.xen.org>
Subject: Re: [edk2] edk2 compile error
On 09/18/16 05:38, Chen, Farrah wrote:
> 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.
>
>
>
>
>
> I also tried:
>
> git clone https://github.com/tianocore/edk2.git
>
> cd edk2
>
> OvmfPkg/build.sh -a X64 -b DEBUG -n 4
> The same error occurred.
> .........................................................................................................................................................
>
> log:
> ......
> Running edk2 build for OvmfPkgX64
> ......
> /home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware
> /ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/CpuE
> xceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandl
> erAsm.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/CpuE
> xceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandl
> erAsm.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/CpuE
> xceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandl
> erAsm.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/CpuE
> xceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandl
> erAsm.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/CpuE
> xceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandl
> erAsm.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/CpuE
> xceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandl
> erAsm.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/firmwar
> e/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/Cpu
> ExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHand
> lerAsm.obj] Error 1
>
>
> build.py...
> : error 7000: Failed to execute command
> make tbuild
> [/home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmwar
> e/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/Cpu
> ExceptionHandlerLib/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/DxeCpuExcep
> tionHandlerLib.inf [X64, GCC44, DEBUG]
>
> - Failed -
RHEL-6 does not have a nasm version that is recent enough to build edk2.
RHEL-6 ships nasm-2.07-*, but edk2 requires nasm-2.10 or later with the GCC toolchain family.
Please see this mailing list thread:
https://www.mail-archive.com/edk2-devel@lists.01.org/msg14420.html
And the resultant docs commit:
https://github.com/tianocore/edk2/commit/9c4dbdff1d56
... Before anyone suggests otherwise, this was not a gratuitous version requirement bump. The edk2 assembly code had already been there, the nasm version bump only documented the status, after the fact.
For RHEL-6 specifically, I suggest to grab a recent enough nasm SRPM from Fedora Koji, and rebuild / install that locally. Better yet, I recommend upgrading to RHEL-7, whose nasm is good enough.
Thanks
Laszlo
prev parent reply other threads:[~2016-09-20 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 3:38 edk2 compile error Chen, Farrah
2016-09-18 15:45 ` Andrew Fish
2016-09-19 0:29 ` Chen, Farrah
2016-09-19 10:51 ` Wei Liu
2016-09-19 10:59 ` Laszlo Ersek
2016-09-20 7:19 ` Chen, Farrah [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=1B925CC0CD9F3341B32D442251E7E1DC36E24CB5@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