[M3devel] help booting CM3 on FreeBSD 4.11?

[Jay]

ps: you'll want something like:
 
C:\dev2\cm3.2\m3-libs\m3core\src>cvs -z3 diff thread.quake
Index: thread.quake
===================================================================
RCS file: /usr/cvs/cm3/m3-libs/m3core/src/thread.quake,v
retrieving revision 1.5
diff -r1.5 thread.quake
40c40
<   "FreeBSD4"   : TRUE,
---
>   "FreeBSD4"   : FALSE,


or
C:\dev2\cm3.2\m3-libs\m3core\src>grep defined thread.quake
    if (NO_USER_THREADS contains TARGET) or ((not defined("NOPTHREAD")) and USE_
PTHREADS{TARGET})
 
 cm3 -DNOPTHREAD 
 

 - Jay




----------------------------------------
> From: jay.krell at cornell.edu
> To: mika at async.caltech.edu; m3devel at elegosoft.com
> Date: Fri, 24 Apr 2009 23:53:09 +0000
> CC: mika at camembert.async.caltech.edu
> Subject: Re: [M3devel] help booting CM3 on FreeBSD 4.11?
>
>
> This /might/ help:
>
>
> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-boot-FreeBSD4-1-userthreads.tar.gz
>
>
> Assuming there are a small number of problems though, the best ways to get more rapid turnaround are to do a cross build or at least first make sure userthreads work on more recent FreeBSD.
>
> - Jay
>
>
>
> ----------------------------------------
>> From: jay.krell at cornell.edu
>> To: mika at async.caltech.edu; m3devel at elegosoft.com
>> CC: mika at camembert.async.caltech.edu
>> Subject: RE: [M3devel] help booting CM3 on FreeBSD 4.11?
>> Date: Fri, 24 Apr 2009 22:40:41 +0000
>>
>>
>>>
>>> Would help if you had pthreads though.
>>
>>
>> IF you have a working-enough pthreads, no matter what library they are in, take a look at:
>>
>>
>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-boot-FreeBSD4-1.tar.gz
>>
>>
>> It's a little gross -- one directory with LOTS of files.
>> And a few subdirectories you don't need.
>>
>>
>> Be sure to look at the start of the Makefile and possibly adjust it.
>> There are some *.sh files, redundant with the Makefile.
>>
>>
>> The output of this is just cm3.
>> You can use that to then build up the system from the bottom of the dependeny tree and on up -- m3cc, m3core, libm3, etc. do-cm3-core.sh/do-cm3-core.py should do that.
>> This is different than "upgrade", which uses an existing m3core/libm3.
>>
>> This is how I do cross builds, both to existing systems and new systems