[cmucl-help] CMUCL 18c building on tru64 5.1

[Fausto Saporito]

Hello Ray,

it goes further... but I have a more troubling error:

; Error: Read error at 8928:
;  "(+ (the vm::offset (* start2 vm:char-bytes/\))"
; Reader error at 8931 on #<Stream for file
"/home/fausap/CMUCL/git-ver/cmucl/src/compiler/generic/vm-tran.lisp">:
; Symbol "CHAR-BYTES" not found in the ALPHA package.

Is this related to unicode thing ?

regards,
Fausto


2014-09-02 18:45 GMT+02:00 Raymond Toy <toy.raymond at gmail.com>:
>
>
>
> On Mon, Sep 1, 2014 at 11:12 PM, Fausto Saporito <fausto.saporito at gmail.com>
> wrote:
>>
>> Hello Raymond,
>>
>> I'll try with git sources.
>> Can I used 20d binaries ?
>
>
>  If you use git sources, you'll have to implement support for 16-bit
> chars on alpha.  That's probably not what you want to do right now.
>
> As for using the 20d binaries with current git sources, that very
> likely won't work.  I would do a git checkout of the 20d sources (tag:
> release-20d), create a branch and go from there, using 20d. In this
> case, be sure to use the 8-bit (non-unicode) binaries and make sure
> :unicode is removed from *features* in the cross-compile script.
>
>> Maybe I should use Linux instead of NetBSD ... this could be better,
>> what do you think ?
>
>
>  I don't use NetBSD, so I can't say. I do, however, use Linux and OSX,
> so at least I'm more familiar with these than NetBSD.
>
> [snip]
>>
>>
>> Start time: Monday, 9/1/14 11:52:41 am [-2], compiling
>> target:compiler/bit-util.
>>
>> ; Python version 1.1, VM version Intel x86/sse2 on 2014-09-01 11:52:41.
>> ; Compiling: /home/fausap/CMUCL/20d/src/compiler/bit-util.lisp
>> 2012-10-27 05:38:08
>>
>> ; Comment: $Header: src/compiler/bit-util.lisp $
>> ;
>> ; Error: Read error at 847:
>> ;  "(do ((i vm:vector-data-offset/\ (1+ i))"
>> ; Reader error at 856 on #<Stream for file
>> "/home/fausap/CMUCL/20d/src/compiler/bit-util.lisp">:
>> ; The symbol "VECTOR-DATA-OFFSET" is not external in the ALPHA package.
>
>
> For now, I would just go change vm:vector-data-offset to
> vm::vector-data-offset (2 colons).  Just to see if that allows you to
> get farther.
> Do the same with the other errors you mention below.
>
> --
> Ray
>