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

Re: [Xen-API] how to compile XCP source?



On 05/03/13 15:35, George Shuklin wrote:
 From yum repositories:
yum install SDL e4fsprogs-libs gcc rpm-build tetex-latex

Ugh, latex is a dependency? That's too bad. I'll add that now, but it would be good if we could find a way to make that optional.

Here minimal list of packages from binpkg.iso and source-1.iso to
satisfy ./prep.sh
(list 1)
kernel-xen-devel-2.6.32.43-0.4.1.xs1.6.10.734.170748.i686.rpm
kernel-kdump-2.6.32.43-0.4.1.xs1.6.10.734.170748.i686.rpm
libev-4.04-1.i686.rpm
blktap-2.0.90.xs726-xs6.1.0.i686.rpm
xen-hypervisor-4.1.3-1.6.10.498.23551.i686.rpm
xen-tools-4.1.3-1.6.10.498.23551.i686.rpm

I've uploaded these files to downloads.xen.org. I've also updated the rpm list in prep.sh.

Files from isos, should be placed in specified location:

(list 2)
  mkdir /javascript/
  mkdir /javascript/jquery
  mkdir /javascript/jquery/treeview

jquery-1.1.3.1.pack.js  -> /javascript/jquery/jquery-1.1.3.1.pack.js
jquery.treeview.zip  -> /javascript/jquery/treeview/jquery.treeview.zip

What requires us to copy these files to a new location? If possible I'd rather fix this requirement than do 'mkdir -p /javascript/jquery/treeview'.

Whole <s>installation</s> compilation guide is looks like this:

1) Install epel:

wget
http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm

rpm -i epel-release-5-4.noarch.rpm
# current part of prep.sh for epel is somehow broken.

2) Install some packages:
yum install SDL e4fsprogs-libs gcc rpm-build tetex-latex

This step is unnecessary, because I added these files to they're installed as part of the group "Development Tools".

3) download prep.sh script
wget https://raw.github.com/mcclurmc/xcp-sdk/master/prep.sh
chmod +x prep.sh

4) download or copy from ISOs files from list 1 (above)
5) install them.

prep.sh does this now. Please check that I've added everything you need.

6) create directories and copy files from list 2 (above)

7) exec ./prep.sh

8) cd xen-api

9) exec fix for pyo/pyc files:
sed -e /.pyo/d -e /.pyc/d -i xapi.spec
#this will be fixed later

Yes, as we discussed earlier, I'm not sure why these aren't getting built. Certainly the right thing to do is to make sure we compile and install the pyc/pyo files, but this is fine for now.

10) make srpm
11) rpm -i /usr/src/redhat/SRPMS/xapi-noarch-0.2-5217.src.rpm
12) rpmbuild -bb /usr/src/redhat/SPECS/xapi.spec

...and few minutes later fresh and shiny xapi waiting for battle:

/usr/src/redhat/RPMS/i386/xapi-tests-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-xenopsd-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-rrd-devel-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-squeezed-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-core-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-datamodel-devel-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-networkd-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-rrdd-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-xenops-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-xe-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-v6d-0.2-5217.i386.rpm
/usr/src/redhat/RPMS/i386/xapi-client-devel-0.2-5217.i386.rpm


It can compile not only xcp-tampa, but even the tampa-lcm head, which
allows to backport.. ... I mean crossport fixes from tampa-lcm to
xcp-tampa.

I hope Mike will adopt those changes to prep.sh.

I have done so, except for the javascript changes. Please check out my repo on github (I'm just in the process of checking that I can download all the necessary rpms from xen.org, but it's taking a while and I don't feel like waiting for it to finish before sending this email).

Also, please feel free to send me a pull request with any changes you'd like to add (in fact, I really encourage this!).

Mike

https://github.com/mcclurmc/xcp-sdk

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


 


Rackspace

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