Brian J. Watson
2004-12-08 19:36:02 UTC
I'm building CI (OPENSSI-RH branch) against OPENSSI
rpm/linux-fc-2.4.22-1.2199.nptl.tar.bz2 module (OPENSSI-FC branch).
I looked into the CVS tree for ci module. OPENSSI-FC-1-1-1 tag is on the
OPENSSI-RH branch so I think there is something wrong with that patch or
with the ci/kernel code.
If you are trying to build a SSI kernel, you need to do the "makerpm/linux-fc-2.4.22-1.2199.nptl.tar.bz2 module (OPENSSI-FC branch).
I looked into the CVS tree for ci module. OPENSSI-FC-1-1-1 tag is on the
OPENSSI-RH branch so I think there is something wrong with that patch or
with the ci/kernel code.
fullkern" in the openssi directory. There is no separate ci build/module.
remember why.
I don't know the state of CI. It is frequently not kept up to date to
build separately since we almost always use it as a part of SSI.
I replaced the broken CI patches with their corresponding versions frombuild separately since we almost always use it as a part of SSI.
the OpenSSI repository, adjusting context as necessary. Everything
applies cleanly, but I'm not certain it will be able to build or run
correctly. Feel free to try it out, Roger, if you're interested.
As John says, the state of the CI patches don't matter as far as OpenSSI
is concerned. It has its own set of kernel patches.
The instructions for building from CVS can be found in
openssi/docs/fedora/devel/INSTALL.cvs in the CVS repository.
This document also explains the temporary weirdness of OPENSSI-FC usingopenssi/docs/fedora/devel/INSTALL.cvs in the CVS repository.
kernel code from the OPENSSI-RH branch, hence OPENSSI-FC-1-1-1 being on
the OPENSSI-RH for all kernel files (and the OPENSSI-FC branch for
everything else).
OPENSSI-DEBIAN is also using the kernel on the OPENSSI-RH branch. This
will change when we start doing the OpenSSI 1.9.x releases with the
2.6.x kernel.
Regards,
Brian