[Openmcl-devel] Failing to build 64 bit ccl/x86

Raymond Wiker rwiker at gmail.com
Tue Aug 18 06:41:48 PDT 2009

On Tue, Aug 18, 2009 at 2:27 PM, John McAleely<john at mcaleely.com> wrote:
>> Wel, getting a fresh checkout will always work.  But it should also
>> work to just rm the binary files (the kernel and the image) before
>> svn up.
> OK, so here's what I think I need to do:
>  - Remove the ccl directory and perform a fresh checkout.
>  - Build ccl & the IDE
> or:
>  (1) Remove all the *fsl files (I've noticed build failures during
> fasl revision changes otherwise)
>  (2) svn revert [ a list of files]
>  (3) svn up
>  (4) Build ccl & the ide.
> In step 1, I worry there are non fsl products of the build (.o files
> perhaps?) that may reach out and break an automaton performing the
> build, and in step 2, I'm not familiar enough with svn to know if svn
> revert --depth infinity will do something useful.
> Given the uncertainties in (1) and (2), I'm now looking for an svn
> incantation that makes my current repository a verbatim copy of the
> remote one with no additions, changes or subtractions. Anyone know of
> any?

I *think* the only binary files that are handled by svn are the
dx86cl, dx86cl64 and their corresponding image files. Thus, it should
be sufficient to handle those. Then, when rebuilding, make sure to use
either :full t or :clean t, which should have the effect of cleaning
out existing fasls.

More information about the Openmcl-devel mailing list