|
xen-ia64-devel
RE: [Xen-ia64-devel] Open GFW Howto
Hi Alex,
We didn't use Debian on our machine. :(
At beginning, we want to put the OGFW into nightly testing too. Then it would
monitor the OGFW's changing, and do normally testing to track its status. So we
want to setup an easy building environment for it. But meeting a lot of
troublesome. :(
Best Regards,
Yongkang You
>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
>Of Alex Williamson
>Sent: Wednesday, November 21, 2007 9:36 PM
>To: Mu, Qin
>Cc: xen-ia64-devel
>Subject: Re: [Xen-ia64-devel] Open GFW Howto
>
>Hi Amy,
>
> I actually went the other way with gcc and explicitly build with
>gcc-3.4. I'm on a Debian Etch build system, here are the specific
>versions of additional packages:
>
>binutils-2.17-3
>gcc-3.4.6-5
>jrockit-R27.3.1-jdk1.5.0_11-linux-ipf
>apache-ant-1.6.5
>ant-contrib-1.0b2
>saxonb8-1-1
>xmlbeans-2.1.0
>
>I apply the attached patch to the source tree to configure my
>environment and setup a path for gcc. My ~/vefi-build/bin directory
>looks like this:
>
>ar -> /usr/bin/ar
>cc -> gcc
>cpp -> g++
>g++ -> /usr/bin/g++-3.4
>gcc -> /usr/bin/gcc-3.4
>ld -> /usr/bin/ld
>
>(the ar and ld ones are probably unnecessary, but left over from
>experimentation)
>
>It's a tricky environment to get setup correctly. Thanks,
>
> Alex
>
>On Wed, 2007-11-21 at 20:10 +0800, Mu, Qin wrote:
>> Hi,
>>
>> I try to build guest firmware of Xen/IA64 in the following build
>> configuration:
>> 1. Build tools:
>> kernel: 2.6.18-53.el5
>> RHEL5 build-in gcc: 4.1.2-14
>> RHEL5 build-in binutils: 2.17.50.0.6-5.el5
>> jrockit-R27.2.0-jdk1.5.10-linux-ipf
>> Apache-ant-1.7.0
>> Ant-contrib-1.0b2
>> Saxonb8-1-1
>> Xmlbeans-2.1.0
>> 2. Source:
>> Efi-vfirmware:
>> http://xenbits.xensource.com/ext/efi-vfirmware.hg
>> Edk2:
>> https://edk2.tianocore.org/svn/edk2/trunk/edk2 -r 2398
>> 3. Runtime Environment:
>> System : Tiger4
>> OS :2.6.18-53.el5xen SMP IA64
>>
>> Although the FV_RECOVERY.bin binary can be lucky generated by
>> following the build instructions depicted in BKM file as the
>> attachment of , the guest domain can't be created using it as guest
>> firmware. A Zombie domain corresponding to that bad domain was listed
>> after typing "xm list". And this zombie can't be removed only after
>> restarting Xend.
>>
>> After switching to using combination of gcc tool of version 4.2 and
>> binutils of version 2.16.1 (both of them are self made by source
>> code), the following build error occurred:
>>
>> sections:
>> [fwimage] SetupBrowser.dll => SetupBrowser.efi
>> [fwimage] FwImage : error
>> E0000:
>/root/efi-vfirmware.hg/edk2-xen/Build/Xen/DEBUG_UNIXGCC/IPF/Edk
>ModulePkg/Universal/UserInterface/SetupBrowser/Dxe/SetupBrowser
>/DEBUG/./SetupBrowser.dll : DOS header signature not found in
>source image
>> [fwimage] ERROR = 2
>>
>> Fortunately, guest domain can be successfully created by using the
>> pre-compiled binary, xenia64-gfw.bin, located under binaries
>directory
>> companying with source.
>>
>> Your help or any suggestion to fix my build problem will be
>> appreciated very much!
>>
>>
>> Amy
>>
>>
>> _______________________________________________
>> Xen-ia64-devel mailing list
>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel
>--
>Alex Williamson HP Open Source & Linux Org.
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
Home