[M3devel] building CM3 on a Raspberry Pi?

mika at async.caltech.edu mika at async.caltech.edu
Mon Oct 14 21:02:52 CEST 2013


More updates...

after I remove mklib, I do get a new compiler built, and I get to this point

ignoring ../src/m3overrides

 ==> /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win/import-libs done

 +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3  -ship -DROOT=/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 +++
--- shipping from AMD64_LINUX ---

 ==> /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win/import-libs done

== package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-libs/m3core ==

 +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -build -DROOT=/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 +++
--- building in AMD64_LINUX ---

ignoring ../src/m3overrides

new source -> compiling RTHooks.i3
../src/runtime/common/RTHooks.i3:15: fatal error:  *** illegal type: 0x6f, at m3cg_lineno 5
compilation terminated.
  m3_backend => 1
m3cc (aka cm3cg) failed compiling: RTHooks.ic
Assembler messages:
Can't open RTHooks.is for reading: No such file or directory
new source -> compiling RT0.i3
../src/runtime/common/RT0.i3:19: fatal error:  *** illegal type: 0x6f, at m3cg_lineno 5
compilation terminated.
  m3_backend => 1
m3cc (aka cm3cg) failed compiling: RT0.ic
Assembler messages:
Can't open RT0.is for reading: No such file or directory
new source -> compiling RuntimeError.i3
../src/runtime/common/RuntimeError.i3:10: fatal error:  *** illegal type: 0x6f, at m3cg_lineno 5
compilation terminated.
  m3_backend => 1
m3cc (aka cm3cg) failed compiling: RuntimeError.ic
Assembler messages:
Can't open RuntimeError.is for reading: No such file or directory
new source -> compiling WordRep.i3
../src/word/WordRep.i3:1: fatal error:  *** illegal type: 0x6f, at m3cg_lineno 5

I've seen this before but don't remember what the issue is.

The compiler is new:

-rwxr-x--- 1 mnystroe rrc 9916732 2013-10-14 11:59 /nfs/site/home/mnystroe/work/cm3/bin/cm3

This is on linux/amd64...


mika writes:
>My toolsets are old, yes.
>
>I tried upgrade.py but you saw that that didn't work either.  
>
>I guess I could go back and re-install from a recent binary image (where
>are the most recent ones?  I only see really old ones on elegosoft...) and
>build everything from scratch.  It's just that all the systems that I
>have M3 on are some sort of production systems and I don't want to mess
>up the installations unnecessarily...   but if it's the only way...
> 
>    Mika
>
>Jay K writes:
>>--_461a9835-225f-448d-96a6-4c651ff66c13_
>>Content-Type: text/plain; charset="iso-8859-1"
>>Content-Transfer-Encoding: quoted-printable
>>
>>Target.i3/m3 look up to date.
>>Is your host toolset very old?
>>
>>https://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-sys/m3middle/src/Ta=
>>rget.i3
>>
>>Revision 1.59: download - view: text=2C markup=2C annotated - select for di=
>>ffs
>>=0A=
>>Sat Jun 19 06:56:32 2010  (3 years=2C 3 months ago) by jkrell
>>=0A=
>>Branches: MAIN
>>=0A=
>>Diff to: previous 1.58: preferred=2C unified
>>=0A=
>>Changes since revision 1.58: +2 -0 lines
>>=0A=
>>add ARMEL_LINUX with correct jmbuf size/align=0A=
>>guessing about alignment=0A=
>>"ARM" is an older ABI=0A=
>>"ARME" is the usual modern ABI=0A=
>>L for little endian=0A=
>>
>>scripts/update.py ?
>>
>> - Jay



More information about the M3devel mailing list