On Mon, 2007-12-17 at 13:30 +0800, Mu, Qin wrote:
> Hi,
>
> A HowTo document is created for the open guest firmware project to help
> users obtain and build from sources.
> Any of your suggestions or comments will be appreciated very much!
Nice work. I think this would be more useful if it were hosted in
the Xen wiki so we could have an online reference and update it as
necessary. A few comments:
Prereqs:
* I think any subversion client and nearly any rev of mercurial is
ok.
* I actually use gcc-3.4 to build and it works fine (I've had
problems w/ gcc-4.1)
* The jrockit version doesn't look like the ones I usually see
from them. I'm using jrockit-R27.3.1-jdk1.5.0_11-linux-ipf.bin.
I don't know how that relates to 5.0.
I don't know if this is useful to others, but since I had problems with
gcc-4.1, which is my system gcc version, I do one more step to make the
build use a different gcc:
diff -r 7988fb818c3b edk2-sparse/Tools/Conf/tools_def.txt
--- a/edk2-sparse/Tools/Conf/tools_def.txt Wed Aug 29 04:11:05 2007 +0200
+++ b/edk2-sparse/Tools/Conf/tools_def.txt Wed Oct 10 15:07:12 2007 -0600
@@ -613,7 +613,7 @@ RELEASE_VS2005PRO_X64_DLINK_FLAGS = /NOL
*_UNIXGCC_IPF_ASM_EXT = .s
*_UNIXGCC_IA32_*_PATH = /usr/bin
-*_UNIXGCC_IPF_*_PATH = /usr/bin
+*_UNIXGCC_IPF_*_PATH = /home/awilliam/vefi-build/bin
#*_UNIXGCC_X64_*_PATH =
/opt/tiano/x86_64-pc-mingw64/x86_64-pc-mingw64/bin
I then have links for cc, cpp, gcc, and g++ to the 3.4 version of the
binaries installed on my system.
Also, another tip, I keep the changes above and changes to my env.sh
file as a patch so that I can apply it quickly to a freshly cloned tree.
I suppose a more advanced way to do it would be to commit the changes to
a local vefi-vfirmware.hg tree, then you could pull that changeset into
your working tree each time. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home