Thread: How do I build kits?

Hi, I've checked out a copy of kusu-kits and was struggling building it/them.

when I try to make from kusu_kits root directory, I alway get the following errors, any suggestion?

Code:

[root@bp860 kits]# make
### Creating kit iso for cacti kit..... ###
make -C /root/simony/kusu_kits/kits/cacti/ iso
make[1]: Entering directory `/root/simony/kusu_kits/kits/cacti/trunk'
sed: read error on packages/kit-cacti/: Is a directory
make[1]: *** [kitinfo] Error 4
make[1]: Leaving directory `/root/simony/kusu_kits/kits/cacti/trunk'
make: *** [/root/simony/kusu_kits/kits/cacti/] Error 2

Even building a specific kit won't work:

Code:

[root@bp860 kits]# make iso KIT=ganglia
### Creating kit iso for ganglia kit..... ###
make -C /root/simony/kusu_kits/kits/ganglia iso
make[1]: Entering directory `/root/simony/kusu_kits/kits/ganglia/trunk'
sed: read error on packages//: Is a directory
make[1]: *** [kitinfo] Error 4
make[1]: Leaving directory `/root/simony/kusu_kits/kits/ganglia/trunk'
make: *** [/root/simony/kusu_kits/kits/ganglia] Error 2
[root@bp860 kits]#

Where are the kits checkout from?

-Liming

Originally Posted by ltsai

Where are the kits checkout from?

-Liming

Code:

[root@bp860 kusu_kits]# svn info
Path: .
URL: http://svn.osgdc.org/kits-repo
Repository Root: http://svn.osgdc.org/kits-repo
Repository UUID: 69e9cef1-a858-0410-896b-dfe2383214dc
Revision: 177
Node Kind: directory
Schedule: normal
Last Changed Author: ltsai
Last Changed Rev: 177
Last Changed Date: 2009-04-15 17:36:01 +0000 (Wed, 15 Apr 2009)

I may found where the problem is. If I try to make it this way:

Code:

[root@bp860 kits]# pwd
/root/simony/kusu_kits/kits
[root@bp860 kits]# make iso KUSU_BUILD_DIST=rhel KUSU_BUILD_DISTVER=5 KUSU_BUILD_ARCH=x86_64

Then I will be able to starting building process. (Hmm, I do have some dependency errors but at least the building process started.) My guess is it seems the Makefile didn't recognize my OS automatically. Thus the KUSU_BUILD_DIST, KUSU_BUILD_DISTVER and KUSU_BUILD_ARCH was not set properly.

Hi

That is correct.

-Liming