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

[John McAleely]

Thank you.

My further investigation was just concluding that svn was not helping  
me. I had not appreciated the full consequences of 'svn up' not  
replacing locally modified files. (I don't think they were  
'conflicted' - they only listed 'M' as their status).

Somehow, my dx86cl64 image had become borked, in ways the dx86cl image  
had not. When I 'reverted' the files dx86cl64 and dx86cl64.image I  
could then build and update them.

Given that each attempt I make appears to fail and require manual  
intervention with svn, I am rapidly concluding that the only way to  
get an automated clean build of ccl is to throw away the subversion  
repository as a first step.

Do any svn gurus know a *reliable* incantation that means my  
repository is an exact replica of the tip of the remote repository?

J


On 18 Aug 2009, at 12:38, Gary Byers wrote:

> As described in <http://trac.clozure.com/openmcl/wiki/UpdatingFromSource 
> >,
> svn doesn't have a good way to resolve the differences between locally
> modified binary files (including the ccl kernel/image files) and  
> updated
> repository versions; "svn update" generally just flags those files  
> as containing conflicts that it can't resolve.
>
> Newer versions of "svn" (1.5.x, 1.6.x) generally do a better job of
> alerting the user to these conflicts (and offer options for resolving
> conflicts during update.)
>
> "svn status" will also show the presence of conflicting files.
>
> "svn revert <file>" will replace the modified local copy of <file>  
> with
> the repository version and convince svn that the apparent conflict has
> been resolved.
>
>
> On Tue, 18 Aug 2009, John McAleely wrote:
>
>> Hi,
>>
>> I updated ccl today. My update script (included below), currently
>> fails to build the trunk's x8664 ccl on my Mac (OS 10.5.8 / Intel).
>>
>> I get the following error message:
>>
>> $ ./dx86cl64
>> Heap image is too new for this kernel.
>> Couldn't load lisp heap image from /Applications/ccl/dx86cl64.image
>>
>> Am I doing something wrong?
>>
>> J
>>
>> ps - the 32 bit image is fine, and reports itself as:
>> Welcome to Clozure Common Lisp Version 1.4-dev-r12621M-trunk
>> (DarwinX8632)!
>>
>> -----
>>
>> script 'update-ccl':
>>
>> #!/bin/bash
>>
>> KERNELS='./dx86cl64 ./dx86cl'
>>
>> function build-ccl()
>> {
>>  local KERNEL=$1
>>  $KERNEL -e "(progn (ccl:rebuild-ccl :full t) (ccl:quit))"
>> }
>>
>> function build-ide()
>> {
>>  local KERNEL=$1
>>
>>  # work around for gui startup issue:
>>  # See <http://clozure.com/pipermail/openmcl-devel/2009-May/009416.html
>> >
>>  echo "(require 'cocoa-application)" | $KERNEL -n
>> }
>>
>> # clean out stale fasls
>> find . -name *fsl -type f -exec rm {} \;
>> # update from svn, wiping out locally built kernel images
>> svn up --accept theirs-full
>>
>> # build each kernel and ide.
>> for KERNEL in $KERNELS; do build-ccl $KERNEL; done
>> for KERNEL in $KERNELS; do build-ide $KERNEL; done
>> _______________________________________________
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
>> http://clozure.com/mailman/listinfo/openmcl-devel
>>
>>
>