[Openmcl-devel] Problem compiling clozure github version on Sierra

[Tim Bradshaw]

I don't know about specifically building 1.11 or 1.12 but I can rebuild the trunk, I think, on a machine running 10.12.6.

The reason for the 'I think' is that I'm only reasonably sure I am doing this from a completely cold system (I nuked all the fasls and fetched the boostrap tarball, but I haven't blown away the entire git tree for instance).

--tim


> On 9 Oct 2017, at 05:01, J Klein <jetmonk at gmail.com> wrote:
> 
> 
> My mac is running 10.12.6 Sierra.  I tried compiling the github version of 64 bit ccl bit using ccl 1.11 (which failed, freezing on optimizers.lisp)
> 
> Then I tried compiling using 1.12 and it failed like this:
> 
> 
> ;Loading #P"/Volumes/Home/Users/Shared/Software/OpenMCL/ccl/level-0/nfasload.dx64fsl"...
> ;Wrote bootstrapping image: #P"/Volumes/Home/Users/Shared/Software/OpenMCL/ccl/x86-boot64.image"
> ;Building lisp-kernel ...
> ;Kernel built successfully.
> > Error: Errors (:signaled 11) reloading boot image:
> >        ;Loading level-1.dx64fsl
> >        ;Loading ./l1-fasls/l1-cl-package.dx64fsl
> >        ;Loading ./l1-fasls/l1-utils.dx64fsl
> >        ;Loading ./l1-fasls/l1-init.dx64fsl
> > [many similar lines deleted]
> >        ;Loading ./l1-fasls/l1-sysio.dx64fsl
> >        ;Loading ./l1-fasls/l1-pathnames.dx64fsl
> >        
> > While executing: rebuild-ccl, in process listener(1).
> > Type :POP to abort, :R for a list of available restarts.
> > Type :? for other options
> 
> 
> A signal 11 is a segfault, I think.
> 
> The 32 bit version seems to have compiled using prepackaged 1.12
> 
> Does this happen for anyone else, or is this a local problem to me?
> 
> 
> -J.Klein
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> https://lists.clozure.com/mailman/listinfo/openmcl-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20171009/33d8d6fc/attachment.htm>