From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id A2D791A1DFB for ; Tue, 20 Sep 2016 00:19:02 -0700 (PDT) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP; 20 Sep 2016 00:19:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,366,1470726000"; d="scan'208";a="11281482" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga005.jf.intel.com with ESMTP; 20 Sep 2016 00:19:02 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 20 Sep 2016 00:19:01 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 20 Sep 2016 00:19:01 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.15]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.118]) with mapi id 14.03.0248.002; Tue, 20 Sep 2016 15:19:01 +0800 From: "Chen, Farrah" To: Laszlo Ersek , "'edk2-devel@ml01.01.org'" CC: "'xen-devel@lists.xen.org'" , Olaf Hering , "wei.liu2@citrix.com" Thread-Topic: [edk2] edk2 compile error Thread-Index: AdIRXVxDf6xB2f8kRaut4adXDo5SvQAxIdmAADrRrcA= Date: Tue, 20 Sep 2016 07:19:01 +0000 Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC36E24CB5@shsmsx102.ccr.corp.intel.com> References: <1B925CC0CD9F3341B32D442251E7E1DC36E16EC8@shsmsx102.ccr.corp.intel.com> <7a819c6f-42ed-f7b7-bd4f-8b98f8cb67b8@redhat.com> In-Reply-To: <7a819c6f-42ed-f7b7-bd4f-8b98f8cb67b8@redhat.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: edk2 compile error X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 07:19:02 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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]=20 Sent: Monday, September 19, 2016 7:00 PM To: Chen, Farrah ; 'edk2-devel@ml01.01.org' Cc: 'xen-devel@lists.xen.org' Subject: Re: [edk2] edk2 compile error On 09/18/16 05:38, Chen, Farrah wrote: > Hi, >=20 > When I compile xen with the latest commit in RHEL 6.7, it failed when mak= e tools. Errors showed when running edk2 build for OvmfPkgX64. > Bisected and this error occurred from commit 8c8b6fb02342f7aa78e611a5f0f6= 3dcf8fbf48f2. >=20 > commit 8c8b6fb02342f7aa78e611a5f0f63dcf8fbf48f2 > Author: Wei Liu > > Date: Tue Sep 6 12:54:47 2016 +0100 >=20 > Config.mk: update OVMF commit >=20 > Signed-off-by: Wei Liu wei.liu2@citrix.com >=20 >=20 > We have updated OVMF to the latest master and cleaned everything before r= ebuilding. >=20 >=20 >=20 > Steps: >=20 > make clean >=20 > make xen -j8 >=20 > ./configure --enable-ovmf >=20 > make tools -j8 >=20 > Then the error occurred. >=20 >=20 >=20 >=20 >=20 > I also tried: >=20 > git clone https://github.com/tianocore/edk2.git >=20 > cd edk2 >=20 > OvmfPkg/build.sh -a X64 -b DEBUG -n 4 > The same error occurred. > .........................................................................= ...........................................................................= ..... >=20 > 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-8c8b6fb= 0-20160912/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC44/X64/Uef= iCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib' > make[7]: ***=20 > [/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 >=20 >=20 > build.py... > : error 7000: Failed to execute command > make tbuild=20 > [/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] >=20 >=20 > build.py... > : error F002: Failed to build module > =20 > /home/www/builds_xen_unstable/xen-src-8c8b6fb0-20160912/tools/firmware > /ovmf-dir-remote/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExcep > tionHandlerLib.inf [X64, GCC44, DEBUG] >=20 > - 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 req= uirement bump. The edk2 assembly code had already been there, the nasm vers= ion bump only documented the status, after the fact. For RHEL-6 specifically, I suggest to grab a recent enough nasm SRPM from F= edora Koji, and rebuild / install that locally. Better yet, I recommend upg= rading to RHEL-7, whose nasm is good enough. Thanks Laszlo