[Openmcl-devel] Building from CVS

Gary Byers gb at clozure.com
Wed Apr 6 03:50:14 UTC 2005



On Tue, 5 Apr 2005, David Steuber wrote:

> On Apr 5, 2005, at 8:51 PM, Gary Byers wrote:
>
> > There have been some pretty drastic ABI changes in the bleeding-edge
> > tree, and you do need a kernel compiled from CVS + the most recent
> > image from the /testing directory to compile current bleeding-edge
> > sources.
>
> I went to fetch a dppcl.image from the ftp server on clozure.com, but
> all I could find was this:
>
> -rw-r--r--    1 1001     0         1936124 Mar 28 05:13
> PPCCL-image-050328.tar.gz

There's a "dppccl-image-050328.tar.gz" in that directory.

> Out of curiosity, how do you deal with these chicken and egg situations
> during development?  The need to fetch a binary to build OpenMCL from
> CVS seems to be a weak link.  Of course my current build process isn't
> very robust either as I compile the kernel first and then attempt to
> use an old image on it to build a new image.  I should probably fix
> that except the old kernel with old image wasn't able to build a new
> image because of that unrecognized opcode.
>

The steps that are necessary to actually make a set of changes like
this are generally complicated and ad-hoc; using a bootstrapping image
(the result of applying those complicated, ad-hoc steps) is certainly
simpler than repeating those steps.



More information about the Openmcl-devel mailing list