[Openmcl-devel] Problem compiling trunk for w64
gb at clozure.com
Thu Apr 28 18:51:40 PDT 2016
On 04/28/2016 05:50 PM, Fabrice Popineau wrote:
> I use the Windows/64 version of ccl.
> I tried to update the trunk (I do it not very often)
> but at this point, recompiling the trunk fails:
Perhaps it does. What did you so to recompiile the trunk, and what
would someone else
do to reproduce the failure ?
> $ ./wx86cl64.exe --no-init
> Error during early application initialization:
> Fault during read of memory address #x2A
> ? for help
>  Clozure CL kernel debugger: B
> current thread: tcr = 0x22350dd0, native thread ID = 0x515c,
> interrupts disabled
> (#x0000000022617E58) #x000000000058008C : #<Function XCMAIN
> #x000000010057EEBF> + 4557
> (#x0000000022617EC8) #x00000000001BF74C : #<Function
> %PASCAL-FUNCTIONS% #x00000001001BF5DF> + 365
> (#x0000000022617F30) #x0000000000000000 : #<Function
> INITIALIZE-INTERACTIVE-STREAMS #x00000001005BCD6F> + 1437
> (#x0000000022617FB8) #x0000000000B78FFC : #<Function
> RESTORE-LISP-POINTERS #x0000000100B78F2F> + 205
>  Clozure CL kernel debugger:
> This is with gcc 5.3.0 from Msys2/MinGW64.
If you use the lisp kernel (wx86cl64.exe) from svn, do you get the same
> Any idea what can cause this ?
I'm not even sure what "this" is ..
Did you download and install CCL and get the error above as soon as you
ran it, or do something else ?
If the latter, can you skip the step of rebuilding the kernel, whose
sources have likely not changed in a fairly long
- download and install CCL
- run it
$ ./wx86cl64.exe --no-init
- rebuild the heap image
? (rebuild-ccl :clean t) #several dozen .lisp files should be compiled
and a new wx86cl64.image
# should be written
- quit that lisp session(via (QUIT) and run the newly-built image with
the distributed kernel. As before:
$ ./wx86cl64.exe # that should try to load a heap image from
"wx86cl64.image", and you just
# built a new version of that file
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel