<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>The "-d5.5" thing is a backup of the package repository. Indeed I find it annoying sometimes, but I mimiced upgrade.sh and I'd have to think it all through again before deleting/changing how it works. I think it makes it easier to back out of a broken change. If you end up with non-working stuff, you copy <FONT face="">pkg-d5.5 back on top of pkg.</FONT><BR>
<BR>
I really strongly suspect update.cmd works. I don't remember if it upgrades...oh, sorry, wrong script I think.<BR>
<STRONG>make-dist.cmd</STRONG>? How about that one?<BR>
Whichever one creates .tar.bz2 files. That's the one I meant. Oops, sorry sorry sorry. :\<BR>
<BR>
<BR>
- Jay<BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
Date: Thu, 20 Sep 2007 22:53:35 +0200<BR>From: dabenavidesd@yahoo.es<BR>To: hosking@cs.purdue.edu; m3devel@elegosoft.com<BR>Subject: Re: [M3devel] NT386 with cm3-5.5 bootstrap compiler<BR><BR><PRE><TT><TT>Hi:<BR><BR>The script upgarde.cmd produced compiler does recognize the LONGINT as a reserved word.<BR><BR>I can get this error when compiling the m2libs of m2tom3 compiler:<BR><BR><BR>new source -> compiling SYSTEM.i3<BR>"..\src\SYSTEM.i3", line 40: Reserved identifier redefined (LONGINT)<BR>1 error encountered<BR><BR>Thanks again<BR><BR><BR><BR>>On Sep 20, 2007, at 11:15 AM, Daniel Alejandro Benavides D. wrote:<BR><BR>> Hi:<BR>> Thanks for your suggestions. I have tried the<BR>> scripts/win/upgrade.cmd, and It does compile and then<BR>> you can execute do-cm3-std.cmd.<BR>><BR>> However I noticed the that script exports a m3core pkg<BR>> to the repository with a m3core-d5.5 like suffix. Not<BR>> sure what is this for.<BR>><BR>> I will test if it can recognize the LONGINT datatype.<BR>><BR>> Also I have a question about Tony's suggestion. The<BR>> packages m3objfile and m3back are not ncessary on the<BR>> stages
you mention for NT386 target?<BR><BR>>Oh, yes, of course they are. Sorry, I forgot about that for NT386.<BR><BR>><BR>> Thanks<BR>><BR>> --- Tony Hosking <<A href="http://compose/?To=hosking@cs.purdue.edu&YY=45995&y5beta=yes&y5beta=yes&order=down&sort=date&pos=0&view=a&head=b" target=_blank>hosking@cs.purdue.edu</A>> escribió:<BR>><BR>>> It strikes me that you may need to sequence as<BR>>> follows to avoid<BR>>> running into having a compiler that does not handle<BR>>> LONGINT.<BR>>><BR>>> Using the "devel_LONGINT_start" tagged versions of<BR>>> m3core and libm3<BR>>> from CVS,<BR>>> using your original compiler, build and ship in the<BR>>> following order:<BR>>><BR>>> m3core (devel_LONGINT_start)<BR>>> libm3 (devel_LONGINT_start)<BR>>> m3middle<BR>>> m3linker<BR>>> m3front<BR>>> m3quake<BR>>> cm3<BR>>><BR>>> Now you have
a new compiler linked against the old<BR>>> m3core.<BR>>><BR>>> Using the new compiler (in cm3/NT386), and the CVS<BR>>> head versions of<BR>>> m3core and libm3,<BR>>> build and ship in the following order:<BR>>><BR>>> m3core (CVS head)<BR>>> libm3 (CVS head)<BR>>> m3middle<BR>>> m3linker<BR>>> m3front<BR>>> m3quake<BR>>> cm3<BR>>><BR>>> Now you have a new compiler linked against the new<BR>>> m3core.<BR>>><BR>>> Copy this new compiler to your CM3 installation bin<BR>>> directory.<BR>>><BR>>> Use this new compiler to rebuild the world.<BR>>><BR>>><BR>>> On Sep 18, 2007, at 8:41 PM, Jay wrote:<BR>>><BR>>>> Daniel, can you try just going back to 5.2.6 and<BR>>> running scripts\win<BR>>>> \update?<BR>>>> You should be able to build the current source the<BR>>> last
"official"<BR>>>> Win32 binaries, as long as you build in the<BR>>> correct order and all,<BR>>>> which the update.cmd does. You know, there's a<BR>>> certain mentality<BR>>>> around bootstrapping and keeping the connection<BR>>> back to the<BR>>>> previous version, that I upheld. As long as you<BR>>> are careful, you<BR>>>> can go from old binaries to new binaries, you<BR>>> don't have to get the<BR>>>> new binaries magically somewhere, though you do<BR>>> need the old<BR>>>> binaries magically from somewhere. :)<BR>>>><BR>>>> Perhaps there's a regression. I can check "later".<BR>>>><BR>>>> - Jay<BR>>>> Date: Wed, 19 Sep 2007 00:49:57 +0200<BR>>>> From: <A href="http://compose/?To=dabenavidesd@yahoo.es&YY=45995&y5beta=yes&y5beta=yes&order=down&sort=date&pos=0&view=a&head=b" target=_blank>dabenavidesd@yahoo.es</A><BR>>>> To: <A href="http://compose/?To=hosking@cs.purdue.edu&YY=45995&y5beta=yes&y5beta=yes&order=down&sort=date&pos=0&view=a&head=b" target=_blank>hosking@cs.purdue.edu</A>; <A href="http://compose/?To=m3devel@elegosoft.com&YY=45995&y5beta=yes&y5beta=yes&order=down&sort=date&pos=0&view=a&head=b" target=_blank>m3devel@elegosoft.com</A><BR>>>> Subject: Re: [M3devel] NT386 with cm3-5.5<BR>>> bootstrap compiler<BR>>>><BR>>>> Hi:<BR>>>><BR>>>> I have compiled with the Jay produced 5.5<BR>>> bootstrap compiler, and<BR>>>> also with 5.1.3a,<BR>>>> 5.2.6 and get the same error.<BR>>>><BR>>>> Thanks<BR>>>><BR>>>>> You need to compile the new m3core with the old<BR>>>
compiler so that the<BR>>>>> symbol is available to you when you compile using<BR>>> the new compiler.<BR>>>>> This is a classical bootstrapping problem.<BR>>>><BR>>>>> On Sep 18, 2007, at 6:30 PM, Daniel Alejandro<BR>>> Benavides D. wrote:<BR>>>><BR>>>>> Hi:<BR>>>>> Thanks for your answer, I have done that and<BR>>> also I get the same<BR>>>>> runtime error<BR>>>>> in the same source file:<BR>>>>><BR>>>>><BR>>>>> C:\cm3-cvs\cm3\m3-libs\m3core>CM3<BR>>>>> --- building in NT386 ---<BR>>>>><BR>>>>> ignoring ..\src\m3overrides<BR>>>>><BR>>>>> new source -> compiling RTHooks.i3<BR>>>>> new source -> compiling RT0.i3<BR>>>>> new source -> compiling RuntimeError.i3<BR>>>>> new source -> compiling
Word.i3<BR>>>>> new source -> compiling RTException.i3<BR>>>>> new source -> compiling RTHooks.m3<BR>>>>> new source -> compiling RT0.m3<BR>>>>> new source -> compiling Compiler.i3<BR>>>>> new source -> compiling RuntimeError.m3<BR>>>>> new source -> compiling Compiler.m3<BR>>>>> new source -> compiling RTAllocator.i3<BR>>>>> new source -> compiling RTType.i3<BR>>>>> new source -> compiling Csetjmp.i3<BR>>>>> new source -> compiling BasicCtypes.i3<BR>>>>> new source -> compiling Ctypes.i3<BR>>>>> new source -> compiling RTMachine.i3<BR>>>>> new source -> compiling RTHeapDep.i3<BR>>>>> new source -> compiling RTHeapRep.i3<BR>>>>> new source -> compiling ThreadF.i3<BR>>>>> new source -> compiling RTOS.i3<BR>>>>> new source
-> compiling RTMisc.i3<BR>>>>> new source -> compiling RTHeap.i3<BR>>>>> new source -> compiling Cstdlib.i3<BR>>>>> new source -> compiling Cstddef.i3<BR>>>>> new source -> compiling RTAllocCnts.i3<BR>>>>> new source -> compiling RTAllocator.m3<BR>>>>> new source -> compiling RTAllocStats.i3<BR>>>>> new source -> compiling Convert.i3<BR>>>>> new source -> compiling TextClass.i3<BR>>>>> new source -> compiling Text.i3<BR>>>>> new source -> compiling RTProcedureSRC.i3<BR>>>>> new source -> compiling Fingerprint.i3<BR>>>>> new source -> compiling RTProcedure.i3<BR>>>>> new source -> compiling RTStack.i3<BR>>>>> new source -> compiling RTAllocStats.m3<BR>>>>> "..\src\runtime\common\RTAllocStats.m3", line<BR>>> 46: undefined
runtime<BR>>>>> symbol !! (R<BR>>>>> THooks.AllocateTracedRef)<BR>>>>><BR>>>>><BR>>>>> ***<BR>>>>> *** runtime error:<BR>>>>> *** Attempt to reference an illegal memory<BR>>> location.<BR>>>>> *** pc = 0x4c4a0d = StartCall + 0xf in<BR>>> ..\src\values\Procedure.m3<BR>>>>> ***<BR>>>>><BR>>>>> Stack trace:<BR>>>>> FP PC Procedure<BR>>>>> --------- ---------<BR>>> -------------------------------<BR>>>>> 0x12f494 0x60b3ce SystemError + 0x66 in<BR>>> ..\src\runtime\NT386<BR>>>>> \RTSignal.m3<BR>>>>> 0x12f4c4 0x4c4a0d StartCall + 0xf in<BR>>> ..\src\values\Procedure.m3<BR>>>>> 0x12f524 0x51beb8 GenRecord + 0x73 in<BR>>> ..\src\builtinOps\New.m3<BR>>>>> 0x12f58c 0x51b8a3 GenRef + 0x111 in<BR>>>
..\src\builtinOps\New.m3<BR>>>>> 0x12f5c8 0x51b70f Gen + 0x12d in<BR>>> ..\src\builtinOps\New.m3<BR>>>>> 0x12f5e0 0x51b4a3 Prep + 0x15 in<BR>>> ..\src\builtinOps\New.m3<BR>>>>> 0x12f600 0x550f08 Prep + 0x75 in<BR>>> ..\src\exprs\CallExpr.m3<BR>>>>> 0x12f61c 0x54312d Prep + 0x54 in<BR>>> ..\src\exprs\Expr.m3<BR>>>>> 0x12f63c 0x544d7f PrepForEmit + 0x81 in<BR>>> ..\src\stmts\AssignStmt.m3<BR>>>>> 0x12f66c 0x54453b Compile + 0xd6 in<BR>>> ..\src\stmts\AssignStmt.m3<BR>>>>> ......... ......... ... more frames ...<BR>>>>><BR>>>>> C:\cm3-cvs\cm3\m3-libs\m3core><BR>>>>>> You need to recompile m3core before compiling<BR>>> with the new<BR>>>> compiler.<BR>>>>><BR>>>>>> On Sep 18, 2007, at 5:29 PM, Daniel Alejandro<BR>>> Benavides D.
wrote:<BR>>>>><BR>>>>>> Hi all:<BR>>>>>> Im getting this runtiem error because the<BR>>> symbol<BR>>>>>><BR>>>>>> missing version stamps -> compiling<BR>>> RTAllocStats.m3<BR>>>>>> "..\src\runtime\common\RTAllocStats.m3", line<BR>>> 46: undefined<BR>>>> runtime<BR>>>>>> symbol !! (R<BR>>>>>> THooks.AllocateTracedRef)<BR>>>>>><BR>>>>>> AllocateTracedRef is not defined in the m3core<BR>>> version</TT></TT></PRE>
<HR SIZE=1>
<BR><FONT face=Verdana size=-2>Sé un Mejor Amante del Cine<BR>¿Quieres saber cómo? <A href="http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html" target=_blank>¡Deja que otras personas te ayuden! </A>.<BR></FONT></BLOCKQUOTE><br /><hr />Make your little one a shining star! <a href='http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us' target='_new'>Shine on!</a></body>
</html>