<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Good.<br><br><br>Yes you can rename anything named NT386 to I386_NT.<br>They are the same.<br><br><br>I suppose maybe..if you upgrade from an NT386 system,<br>the result should be NT386, and produce NT386 by default.<br>That only explicitly I386_NT or cross (which requires explicit<br>target anyway) should switch to the new name.<br><br><br>I'd want any new users/installs to use I386_NT, but perhaps<br>it is rude to switch existing users/installs.<br><br><br>Probably what I did is default to the new names unless CM3_TARGET is set.<br><br><br>Does upgrade.py and do-cm3-all.py buildship work for you now?<br><br><br> - Jay<br><br><div><hr id="stopSpelling">From: rcolebur@SCIRES.COM<br>To: jay.krell@cornell.edu; m3devel@elegosoft.com<br>Subject: RE: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>Date: Wed, 25 Sep 2013 21:34:39 +0000<br><br>
<style><!--
.ExternalClass .ecxshape {
}
--></style><style><!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:blue;
text-decoration:underline;
}
.ExternalClass span.ecxMsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}
.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxMsoAcetate, .ExternalClass li.ecxMsoAcetate, .ExternalClass div.ecxMsoAcetate {
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
}
.ExternalClass span.ecxBalloonTextChar {
font-family:"Tahoma","sans-serif";
}
.ExternalClass span.ecxEmailStyle20 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}
.ExternalClass div.ecxWordSection1 {
}
--></style>
<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Jay, Rodney, et al:</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">I am pleased to finally report
<b>SUCCESS</b> with rebuilding my cm3 on 32-bit Windows XP !</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Thanks for the help.</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">I did have to restore my
<b>bin</b>, <b>lib</b>, & <b>pkg</b> folders from backup in order to get the rebuild to succeed after the last round of patches. But, it works now.</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">I do have a question though. I’m finding that I have to set an environment variable,
<b>CM3_TARGET=NT386</b>; otherwise, the compiler is trying to target <b>I386_NT</b> and since all my target folders in
<b>pkg</b> and in the sandbox are <b>NT386</b>, I run into all sorts of problems.
</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><b><u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">If
</span></u></b><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">we should be using the new “I386_NT” name instead of “NT386”, can I just rename all my
<u>NT386</u> folders to be <u>I386_NT</u> and stop setting the CM3_TARGET variable, or will there be problems with this approach?</span></b></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">FYI, here is the version info on my rebuilt compiler (without setting the CM3_TARGET variable):</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Critical Mass Modula-3 version d5.9.0</span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> last updated: 2010-07-21</span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> compiled: 2013-09-25 04:53:00</span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> configuration: .\cm3.cfg</span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> host: NT386</span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">defaulting to native build: I386_NT</span></p>
<p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> target: I386_NT</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Thanks,</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Randy Coleburn</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ecxMsoNormal" style=""><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";"> jayk123@hotmail.com [mailto:jayk123@hotmail.com]
<b>On Behalf Of </b>Jay K<br>
<b>Sent:</b> Tuesday, September 24, 2013 2:18 AM<br>
<b>To:</b> Coleburn, Randy; Rodney M. Bates; m3devel<br>
<b>Subject:</b> EXT:RE: [M3devel] EXT:RE: [M3commit] CVS Update: cm3</span></p>
</div>
</div>
<p class="ecxMsoNormal" style=""> </p>
<div>
<p class="ecxMsoNormal" style=""><span style="font-family:"Calibri","sans-serif";">And, my apologies, the upgrade procedure is rather in-place/destructive.<br>
You must have backup to try again.<br>
I kind of want to fix this.<br>
The way make-dist.py works is similar but<br>
fixes this -- it builds into new temporary locations.<br>
Upgrade could/should do that, and then copy back later on.<br>
<br>
- Jay<br>
</span></p>
<div>
<div class="ecxMsoNormal" style="text-align:center;" align="center">
<span style="font-family:"Calibri","sans-serif";">
<hr id="ecxstopSpelling" align="center" size="3" width="100%">
</span></div>
<p class="ecxMsoNormal" style="">
<span style="font-family:"Calibri","sans-serif";">From: <a href="mailto:jay.krell@cornell.edu">
jay.krell@cornell.edu</a><br>
To: <a href="mailto:rcolebur@scires.com">rcolebur@scires.com</a>; <a href="mailto:rodney_bates@lcwb.coop">
rodney_bates@lcwb.coop</a>; <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a><br>
Date: Tue, 24 Sep 2013 04:21:02 +0000<br>
Subject: Re: [M3devel] EXT:RE: [M3commit] CVS Update: cm3</span></p>
<div>
<p class="ecxMsoNormal" style="">
<span style="font-family:"Calibri","sans-serif";">Please update m3-sys/m3front/src/misc/CG.m3 and try again.<br>
I need to do more testing here though.. I'll try AMD64_DARWIN and I386_DARWIN<br>
with "my change" (which is just a partial undo).<br>
<br>
- Jay<br>
<br>
</span></p>
<div>
<div class="ecxMsoNormal" style="text-align:center;" align="center">
<span style="font-family:"Calibri","sans-serif";">
<hr id="ecxstopSpelling" align="center" size="3" width="100%">
</span></div>
<p class="ecxMsoNormal" style="">
<span style="font-family:"Calibri","sans-serif";">From: <a href="mailto:jay.krell@cornell.edu">
jay.krell@cornell.edu</a><br>
To: <a href="mailto:rcolebur@scires.com">rcolebur@scires.com</a>; <a href="mailto:rodney_bates@lcwb.coop">
rodney_bates@lcwb.coop</a>; <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a><br>
Date: Tue, 24 Sep 2013 03:56:58 +0000<br>
Subject: Re: [M3devel] EXT:RE: [M3commit] CVS Update: cm3</span></p>
<div>
<p class="ecxMsoNormal" style="">
<span style="font-family:"Calibri","sans-serif";">NT386 works fine on 64bit Windows..<br>
The AMD64_NT target has a problem currently that I hope to figure out soon..<br>
<br>
What version of cm3?<br>
A release?<br>
A random cvs upd time?<br>
<br>
- Jay<br>
<br>
</span></p>
<div>
<p class="ecxMsoNormal" style=""><span style="font-family:"Calibri","sans-serif";">> From:
<a href="mailto:rcolebur@SCIRES.COM">rcolebur@SCIRES.COM</a><br>
> To: <a href="mailto:rodney_bates@lcwb.coop">rodney_bates@lcwb.coop</a>; <a href="mailto:m3devel@elegosoft.com">
m3devel@elegosoft.com</a><br>
> Date: Tue, 24 Sep 2013 01:48:57 +0000<br>
> Subject: Re: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>
> <br>
> Rodney:<br>
> <br>
> For this situation, I'm compiling on an old 32-bit Windows XP computer targeting NT386.
<br>
> The computer has Microsoft Visual Studio 2008 Express installed (needed for the linker and the C compiler).<br>
> Thus, I am running the integrated backend, I believe.<br>
> <br>
> I've kept this computer backlevel from the HEAD branch for quite some time because I had to maintain exact synchronization with the build environment for some stuff I've been supporting in production.<br>
> <br>
> That support requirement has gone away, so I want to update to the latest (and greatest?) compiler and sources. My sandbox is now current wrt the HEAD branch via CVS.<br>
> <br>
> I've succeeded in making it thru the first stage of the compiler rebuild process, but now in stage #2 I get the error that I reported.<br>
> <br>
> In the past, I've always been able to update via CVS then rebuild everything, but perhaps I've waited too long in this case, or maybe I've uncovered some bug(s).<br>
> <br>
> After I get things working on this 32-bit XP machine (see I'm trying to be optimistic), I plan to update on a 64-bit Windows7 computer. I'm not sure though if I can start with my 32-bit implementation and simply rebuild on the 64-bit machine to bump up to
64-bit binaries, or if more adjustment or a different approach is required.<br>
> <br>
> Thanks for your insight and help!<br>
> <br>
> Thanks,<br>
> Randy Coleburn<br>
> <br>
> -----Original Message-----<br>
> From: Rodney M. Bates [<a href="mailto:rodney_bates@lcwb.coop">mailto:rodney_bates@lcwb.coop</a>]
<br>
> Sent: Monday, September 23, 2013 9:32 PM<br>
> To: <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a><br>
> Subject: EXT:Re: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>
> <br>
> Hmm, I'm looking at this. I recently committed a compiler front-end change that made this error go away, for different cases. It's in m3-sys/m3front/src/misc/CG.m3, version<br>
> 1.15.2.5 in the release and 1.43 in the head. Are you compiling with one of these?<br>
> <br>
> I reread it, and my change still looks right to me. The message helpfully gives important information, and ScanTypes seems to be being asked to find an unsigned integer code-generator type that has alignment at least 64, but fits in a 32-bit word. And this
for a global variable of type BOOLEAN and size 8 (bits). So the 64-bit alignment request doesn't seem sensible. I can't guess where the 32-bit requirement would have come from. Is it a 32-bit target you are compiling for?<br>
> <br>
> RTAllocator.m3 compiles fine on my AMD64_LINUX machine.<br>
> <br>
> <br>
> <br>
> On 09/23/2013 06:03 PM, Coleburn, Randy wrote:<br>
> > Jay:<br>
> ><br>
> > Thanks. I've applied the edit you suggested and was able to finish the compile for mklib.<br>
> ><br>
> > *Do you want me to commit this change via CVS to the repository?*<br>
> ><br>
> > Now, that gets me thru stage #1 of the rebuild.<br>
> ><br>
> > In stage #2, the packages and their order that I am attempting to compile are:<br>
> ><br>
> > Packages to be processed:<br>
> ><br>
> > ------------------------<br>
> ><br>
> > m3-win\import-libs<br>
> ><br>
> > m3-sys\m3cc<br>
> ><br>
> > m3-libs\m3core<br>
> ><br>
> > m3-libs\libm3<br>
> ><br>
> > m3-libs\sysutils<br>
> ><br>
> > m3-sys\m3middle<br>
> ><br>
> > m3-sys\m3objfile<br>
> ><br>
> > m3-sys\m3linker<br>
> ><br>
> > m3-sys\m3back<br>
> ><br>
> > m3-sys\m3cggen<br>
> ><br>
> > m3-sys\m3front<br>
> ><br>
> > m3-sys\m3quake<br>
> ><br>
> > m3-sys\cm3<br>
> ><br>
> > m3-sys\m3cgcat<br>
> ><br>
> > m3-sys\mklib<br>
> ><br>
> > But, skipping packages: m3cc<br>
> ><br>
> > ---END-of-List---<br>
> ><br>
> > *Things go fine until I get to m3core. I get an internal code generator error. *See error below:<br>
> ><br>
> > --- processing package "m3-libs\m3core" ---<br>
> ><br>
> > --- purging derived files from NT386 ---<br>
> ><br>
> > --- cleaning NT386 ---<br>
> ><br>
> > ignoring ..\src\m3overrides<br>
> ><br>
> > --- building in NT386 ---<br>
> ><br>
> > ignoring ..\src\m3overrides<br>
> ><br>
> > new source -> compiling RTHooks.i3<br>
> ><br>
> > new source -> compiling RT0.i3<br>
> ><br>
> > new source -> compiling RuntimeError.i3<br>
> ><br>
> > new source -> compiling WordRep.i3<br>
> ><br>
> > new source -> compiling Word.i3<br>
> ><br>
> > new source -> compiling RTException.i3<br>
> ><br>
> > new source -> compiling RTHooks.m3<br>
> ><br>
> > new source -> compiling RT0.m3<br>
> ><br>
> > new source -> compiling Compiler.i3<br>
> ><br>
> > new source -> compiling RuntimeError.m3<br>
> ><br>
> > new source -> compiling Compiler.m3<br>
> ><br>
> > new source -> compiling RTAllocator.i3<br>
> ><br>
> > new source -> compiling RTType.i3<br>
> ><br>
> > new source -> compiling RTHeapRep.i3<br>
> ><br>
> > new source -> compiling FloatMode.i3<br>
> ><br>
> > new source -> compiling RTThread.i3<br>
> ><br>
> > new source -> compiling Scheduler.i3<br>
> ><br>
> > new source -> compiling RTOS.i3<br>
> ><br>
> > new source -> compiling RTMisc.i3<br>
> ><br>
> > new source -> compiling Cstdlib.i3<br>
> ><br>
> > new source -> compiling Cstddef.i3<br>
> ><br>
> > new source -> compiling LongRep.i3<br>
> ><br>
> > new source -> compiling Long.i3<br>
> ><br>
> > new source -> compiling BasicCtypes.i3<br>
> ><br>
> > new source -> compiling Ctypes.i3<br>
> ><br>
> > new source -> compiling RTAllocCnts.i3<br>
> ><br>
> > new source -> compiling RTAllocator.m3<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 95: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 209: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 231: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 248: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 270: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 303: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > "..\src\runtime\common\RTAllocator.m3", line 324: ** INTERNAL CG ERROR <br>
> > *** unable to find integer type? type=Word.32 s/o/a=8/416/64<br>
> ><br>
> > 7 errors encountered<br>
> ><br>
> > Thanks for your continued help,<br>
> ><br>
> > Randy Coleburn<br>
> ><br>
> > *From:*jayk123@hotmail.com [<a href="mailto:jayk123@hotmail.com">mailto:jayk123@hotmail.com</a>] *On Behalf Of
<br>
> > *Jay K<br>
> > *Sent:* Monday, September 23, 2013 5:48 PM<br>
> > *To:* Coleburn, Randy; m3devel<br>
> > *Subject:* EXT:RE: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>
> ><br>
> > Sorry, you are right I missed it.<br>
> ><br>
> > I'll fix it tonight probably.<br>
> ><br>
> ><br>
> > Here it is:<br>
> > CONST IMAGE_FILE_MACHINE_AMD64 = 16_8664 (* from <br>
> > m3core/src/win32/winnt.i3 *)<br>
> ><br>
> > and change "WinNT.IMAGE_FILE_MACHINE_AMD64" to just "IMAGE_FILE_MACHINE_AMD64".<br>
> ><br>
> > - Jay<br>
> ><br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > --------<br>
> --<br>
> ><br>
> > From: <a href="mailto:rcolebur@SCIRES.COM">rcolebur@SCIRES.COM</a> <<a href="mailto:rcolebur@SCIRES.COM">mailto:rcolebur@SCIRES.COM</a>><br>
> > To: <a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a> <<a href="mailto:jay.krell@cornell.edu">mailto:jay.krell@cornell.edu</a>>;
<br>
> > <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a> <<a href="mailto:m3devel@elegosoft.com">mailto:m3devel@elegosoft.com</a>><br>
> > Subject: RE: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>
> > Date: Mon, 23 Sep 2013 21:38:14 +0000<br>
> ><br>
> > Jay:<br>
> ><br>
> > My "m3-sys/mklib/src/Main.m3" is showing current wrt the HEAD branch in CVS.<br>
> ><br>
> > CVS indicates there is no update for me to obtain.<br>
> ><br>
> > My file is 850 lines in length.<br>
> ><br>
> > Did you commit changes to this file? If you did, they aren't coming thru for me.<br>
> ><br>
> > So, the error persists:<br>
> ><br>
> > "..\src\Main.m3", line 87: unknown qualification '.' <br>
> > (IMAGE_FILE_MACHINE_AMD64)<br>
> ><br>
> > Please advise.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Randy Coleburn<br>
> ><br>
> > *From:*jayk123@hotmail.com <<a href="mailto:jayk123@hotmail.com">mailto:jayk123@hotmail.com</a>>
<br>
> > [<a href="mailto:jayk123@hotmail.com">mailto:jayk123@hotmail.com</a>] *On Behalf Of *Jay K<br>
> > *Sent:* Sunday, September 22, 2013 1:43 AM<br>
> > *To:* Coleburn, Randy; m3devel<br>
> > *Subject:* EXT:RE: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>
> ><br>
> > Right.<br>
> > cvs upd m3-sys/mklib/src/Main.m3 should fix it.<br>
> ><br>
> ><br>
> > I know the problem with the Python. It is dependent on newer cm3 that prints "host", rather than, I guess, the sniffing it used to do. I'm not sure I'll fix it. I have to go back and install the older versions and go through the workflow myself and then
I can improve/fix it.<br>
> ><br>
> ><br>
> > What does cm3 -version print?<br>
> ><br>
> > > or that my m3core is too old to be able to perform an upgrade<br>
> ><br>
> ><br>
> > Most likely it will work. mklib I recall is last in the bootstrap phase, so you are 99.99% there.<br>
> ><br>
> ><br>
> > The system is written in itself. An excellent feature.<br>
> > There are always therefore these problems, and always we should probably gradually require a newer build.<br>
> > When there isn't a new enough native install, or any at all, a cross build is the solution.<br>
> > I have "crossed" countless times at this point and can vouch for its viability.<br>
> > We cannot/must not support arbitrarily old. For example, building from the old/stable 3.6 release is probably irrecovably broken by now. Because the system has gone so long with relatively little change, these aspects become hidden to most people and they
consider it a problem/bug when they come up, when they are actually perfectly natural results of the system using itself, and incurring any changes.<br>
> ><br>
> ><br>
> > - Jay<br>
> ><br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > --------<br>
> --<br>
> ><br>
> > From: <a href="mailto:rcolebur@SCIRES.COM">rcolebur@SCIRES.COM</a> <<a href="mailto:rcolebur@SCIRES.COM">mailto:rcolebur@SCIRES.COM</a>><br>
> > To: <a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a> <<a href="mailto:jay.krell@cornell.edu">mailto:jay.krell@cornell.edu</a>>;
<br>
> > <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a> <<a href="mailto:m3devel@elegosoft.com">mailto:m3devel@elegosoft.com</a>><br>
> > Date: Sun, 22 Sep 2013 05:35:15 +0000<br>
> > Subject: Re: [M3devel] EXT:RE: [M3commit] CVS Update: cm3<br>
> ><br>
> > Based on your response, I guess that as soon as I can get this thing to build, my pkg tree will get updated with the newer Ctypes, but right now I'm stuck on this error in building mklib:<br>
> ><br>
> > "..\src\Main.m3", line 87: unknown qualification '.' <br>
> > (IMAGE_FILE_MACHINE_AMD64)<br>
> ><br>
> > In your prior response you stated, "I updated mklib to contain the definition itself instead of using m3core."<br>
> ><br>
> > Does that mean you've fixed the problem, or that I have more work to do, or that my m3core is too old to be able to perform an upgrade?<br>
> ><br>
> > I'm not able to use the python scripts due to the following error:<br>
> > C:\cm3\Sandbox\cm3\scripts\python>upgrade.py<br>
> > Traceback (most recent call last):<br>
> > File "C:\cm3\Sandbox\cm3\scripts\python\upgrade.py", line 4, in <module><br>
> > import pylib<br>
> > File "C:\cm3\Sandbox\cm3\scripts\python\pylib.py", line 650, in <module><br>
> > if Host.endswith("_NT") or Host == "NT386":<br>
> > AttributeError: 'NoneType' object has no attribute 'endswith'<br>
> ><br>
> > So, I'm working with my CMD files and doing stuff by hand.<br>
> ><br>
> > --Randy Coleburn<br>
> ><br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > --------<br>
> --<br>
> ><br>
> > *From:*jayk123@hotmail.com <<a href="mailto:jayk123@hotmail.com">mailto:jayk123@hotmail.com</a>>
<br>
> > [jayk123@hotmail.com] on behalf of Jay K [jay.krell@cornell.edu]<br>
> > *Sent:* Sunday, September 22, 2013 1:14 AM<br>
> > *To:* Coleburn, Randy; m3devel<br>
> > *Subject:* EXT:RE: [M3devel] [M3commit] CVS Update: cm3<br>
> ><br>
> > <a href="https://dcvs.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/m3core/src/C" target="_blank">
https://dcvs.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/m3core/src/C</a><br>
> > /Common/Ctypes.i3<br>
> ><br>
> ><br>
> > - Jay<br>
> ><br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > --------<br>
> --<br>
> ><br>
> > From: <a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a> <<a href="mailto:jay.krell@cornell.edu">mailto:jay.krell@cornell.edu</a>><br>
> > To: <a href="mailto:rcolebur@scires.com">rcolebur@scires.com</a> <<a href="mailto:rcolebur@scires.com">mailto:rcolebur@scires.com</a>>;
<br>
> > <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a> <<a href="mailto:m3devel@elegosoft.com">mailto:m3devel@elegosoft.com</a>><br>
> > Date: Sun, 22 Sep 2013 05:03:17 +0000<br>
> > Subject: Re: [M3devel] [M3commit] CVS Update: cm3<br>
> ><br>
> > It is cm3/m3-libs/m3core/src/C/Common/Ctypes.i3 in the source tree or \cm3\pkg\m3core\NT386\Ctypes.i3 in an install.<br>
> > In the first pass of upgrade, it comes from the install, so can be old..but how old?<br>
> > After the first pass, it comes from the source tree.<br>
> ><br>
> > - Jay<br>
> ><br>
> ><br>
> ><br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > --------<br>
> --<br>
> ><br>
> > From: <a href="mailto:rcolebur@SCIRES.COM">rcolebur@SCIRES.COM</a> <<a href="mailto:rcolebur@SCIRES.COM">mailto:rcolebur@SCIRES.COM</a>><br>
> > To: <a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a> <<a href="mailto:jay.krell@cornell.edu">mailto:jay.krell@cornell.edu</a>>;
<br>
> > <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a> <<a href="mailto:m3devel@elegosoft.com">mailto:m3devel@elegosoft.com</a>><br>
> > Date: Sun, 22 Sep 2013 04:57:01 +0000<br>
> > Subject: Re: [M3devel] [M3commit] CVS Update: cm3<br>
> ><br>
> > Jay:<br>
> ><br>
> > Where is the CTypes file coming from?<br>
> > I've updated my entire Sandbox via CVS to be current with the head branch, so if CTypes is in there, what I have should be current.<br>
> > If CTypes is coming from somewhere else, then please explain where and what I need to do in order to update.<br>
> > The computer I'm using for this build is a 32-bit WinXP machine. It has Visual Studio Express 2008 installed on it.<br>
> ><br>
> > --Randy Coleburn<br>
> ><br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > ----------------------------------------------------------------------<br>
> > --------<br>
> --<br>
> ><br>
> > *From:*jayk123@hotmail.com <<a href="mailto:jayk123@hotmail.com">mailto:jayk123@hotmail.com</a>>
<br>
> > [jayk123@hotmail.com] on behalf of Jay K [jay.krell@cornell.edu]<br>
> > *Sent:* Sunday, September 22, 2013 12:41 AM<br>
> > *To:* m3devel; Coleburn, Randy<br>
> > *Subject:* EXT:RE: [M3commit] CVS Update: cm3<br>
> ><br>
> > Fyi, Your CTypes is over 5 years old. It predates Thu May 29 14:43:18 2008 .<br>
> > I realize in this case, it is trivial to support older, but...<br>
> ><br>
> > - Jay<br>
> ><br>
> >> Date: Sun, 22 Sep 2013 06:35:02 +0000 To:m3commit@elegosoft.com <br>
> >> <<a href="mailto:m3commit@elegosoft.com">mailto:m3commit@elegosoft.com</a>> From:rcoleburn@elego.de
<br>
> >> <<a href="mailto:rcoleburn@elego.de">mailto:rcoleburn@elego.de</a>><br>
> >> Subject: [M3commit] CVS Update: cm3<br>
> >><br>
> >> CVSROOT: /usr/cvs<br>
> >> Changes by: rcoleburn@birch. 13/09/22 06:35:02<br>
> >><br>
> >> Modified files:<br>
> >> cm3/m3-sys/m3back/src/: M3CC.i3<br>
> >><br>
> >> Log message:<br>
> >> fix broken compilation, line 6, change "ctypes.unsigned" to be "ctypes.unsigned_int"<br>
> >><br>
> ><br>
> </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div> </div></body>
</html>