public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chen, Farrah" <farrah.chen@intel.com>
To: "afish@apple.com" <afish@apple.com>
Cc: "edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Hao, Xudong" <xudong.hao@intel.com>
Subject: Re: edk2 compile error
Date: Mon, 19 Sep 2016 00:29:08 +0000	[thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC36E2092A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <5E252CA7-1B99-4025-A039-9E9BEF0ACC2F@apple.com>

FYI.

Thanks,
Fan Chen

-----Original Message-----
From: afish@apple.com [mailto:afish@apple.com] 
Sent: Sunday, September 18, 2016 11:45 PM
To: Chen, Farrah <farrah.chen@intel.com>
Cc: edk2-devel@ml01.01.org; xen-devel@lists.xen.org
Subject: Re: [edk2] edk2 compile error


> On Sep 17, 2016, at 8:38 PM, Chen, Farrah <farrah.chen@intel.com> 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/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

Can you attach a copy of the failing ExceptionHandlerAsm.iii as it is the output of the preprocessor. 

Thanks,

Andrew Fish

> 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 -
> 
> 
> Thanks,
> Fan Chen
> 
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel



  reply	other threads:[~2016-09-19  0:29 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 [this message]
2016-09-19 10:51 ` Wei Liu
2016-09-19 10:59 ` Laszlo Ersek
2016-09-20  7:19   ` 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=1B925CC0CD9F3341B32D442251E7E1DC36E2092A@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