[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] OVMF compile error



Really fix the address this time...

On Tue, Sep 13, 2016 at 10:39:02AM +0100, Wei Liu wrote:
> Hi,
> 
> I just realise that your xen-devel address is wrong.
> 
> It should be xen-devel@xxxxxxxxxxxxx.
> 
> On Tue, Sep 13, 2016 at 03:30:51AM +0000, Chen, Farrah wrote:
> > Hi Wei,
> > 
> > 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.
> > 
> 
> Can you please attach attach the file that failed to build here?
> 
> Looking at the package name it is likely to be a bug in upstream edk2. I
> think it would be suitable to report it upstream. But I would like to
> check the file first.
> 
> Wei.
> 
> > 
> > Thanks,
> > Fan Chen
> > 
> > 
> > -----Original Message-----
> > From: Wei Liu [mailto:wei.liu2@xxxxxxxxxx] 
> > Sent: Monday, September 12, 2016 3:53 PM
> > To: Chen, Farrah <farrah.chen@xxxxxxxxx>
> > Cc: xen-devel-request@xxxxxxxxxxxxx; Hao, Xudong <xudong.hao@xxxxxxxxx>; 
> > wei.liu2@xxxxxxxxxx
> > Subject: Re: OVMF compile error
> > 
> > Hi
> > 
> > On Mon, Sep 12, 2016 at 07:31:42AM +0000, 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@xxxxxxxxxx>
> > > Date:   Tue Sep 6 12:54:47 2016 +0100
> > > 
> > >     Config.mk: update OVMF commit
> > > 
> > > Signed-off-by: Wei Liu wei.liu2@xxxxxxxxxx<mailto:wei.liu2@xxxxxxxxxx>
> > > 
> > > ………………………………………………………………………………………………………………………………………
> > > 
> > > make_tools.log:
> > > ……
> > > /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
> > > 
> > 
> > 
> > There seems to be something wrong with the generated file. It's likely to 
> > be a bug in upstream.
> > 
> > How did you compile OVMF? Did you clean everything before rebuilding?
> > Could you try updating OVMF to the latest master?
> > 
> > Wei.
> > 
> > > 
> > > 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 –
> > > 
> > > 
> > > Best Regards,
> > > Fan Chen
> > > 
> > > 
> > 
> > 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.