<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'>Yes, exactly, that's what I was trying to say, in my later/last mail.<BR> <BR><br>Yes the compability is definitely two-way.<br>There is a one to one mapping back and forth.<br>cm3 goes with cm3cg; cm3cg goes with cm3.<br>Neither is compatible with older nor necessarily newer versions.<BR> <BR><br>They would be statically linked together if not for the GPL.<BR> <BR><br>When I first placed m3cc in pkginfo.txt years ago, I was only thinking<br>of build order and, like, "override".<BR> <BR><br>m3cc imports nothing and nothing imports m3cc.<br>In the Modula-3 module/library/interface sense.<BR> <BR><br>It can be built when you have nothing.<br>So I figured put it nearly first.<BR> <BR><br>Only now today did I consider the shipping order.<br>It should be shipped adjacent to cm3, either right before or right after.<BR> <BR><br>If you split build and ship, then it can still be built early,<br>or at almost any time.<BR> <BR><br>But we have one ordering for build and ship, so let the shipping order decide.<BR> <BR><br>I still don't like INSTALL_CM3_IN_BIN and I'd still like to remove it.<BR>I still think it broke upgrade.py.<BR>I can workaround. But I'd like to remove the environment variable check.<BR> <BR> <BR>There are many order dependencies in build and ship. This is just one.<BR> <BR> <BR> - Jay<br><br><br><br> <BR><div>> Date: Sun, 31 May 2015 22:28:13 -0500<br>> From: rodney_bates@lcwb.coop<br>> To: m3devel@elegosoft.com; adacore@marino.st<br>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp (0x100), expected 0x110<br>> <br>> I am quite sure that the cm3/cm3cg incompatibility is two-way, i.e.,<br>> both must be new or both old. So, I would expect INSTALL_CM3_IN_BIN=yes<br>> to fail regardless of the order of building the two.<br>> <br>> OTOH, if cm3 were built and shipped, then m3cc came immediately after,<br>> it should work, because m3cc contains no Modula-3 code, and the new<br>> cm3 would not, when building it, run cm3cg. After that, there would<br>> be a consistent set. for further compiles. But any package containing<br>> M3 code built between cm3 and m3cc would fail.<br>> <br>> On 05/31/2015 05:15 PM, Jay wrote:<br>> > I think now it might not be the problem. Could be m3cc needs to be later in pkginfo.txt. I have to try later.<br>> ><br>> > - Jay<br>> ><br>> > On May 31, 2015, at 10:59 AM, John Marino <adacore@marino.st> wrote:<br>> ><br>> >> I removed "INSTALL_CM3_IN_BIN=yes" after reading the thread about it.<br>> >> Should I put it back? From the last response I'm guessing that wasn't<br>> >> the problem.<br>> >><br>> >> John<br>> >><br>> >><br>> >> On 5/31/2015 19:09, Jay K wrote:<br>> >>> Oh probably the problem is using the backend premature actually.<br>> >>> Darn, I can't help right now.<br>> >>><br>> >>> - Jay<br>> >>><br>> >>><br>> >>><br>> >>> ------------------------------------------------------------------------<br>> >>> From: jay.krell@cornell.edu<br>> >>> To: adacore@marino.st; m3devel@elegosoft.com<br>> >>> Date: Sun, 31 May 2015 16:45:42 +0000<br>> >>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp<br>> >>> (0x100), expected 0x110<br>> >>><br>> >>> Hm. Strange. I need to read more closely. I see it skipping shipping,<br>> >>> but my read was it didn't try that.<br>> >>> So.. with INSTALL_CM3_IN_BIN=yes?<br>> >>> I need to try this all, and "fix" it to set that. The whole thing in<br>> >>> m3cc/src/m3makefile is relatively<br>> >>> new vs. when I was actively using all this. :(<br>> >>><br>> >>> - Jay<br>> >>><br>> >>><br>> >>>> Date: Sun, 31 May 2015 16:57:02 +0200<br>> >>>> From: adacore@marino.st<br>> >>>> To: jay.krell@cornell.edu; m3devel@elegosoft.com<br>> >>>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp<br>> >>> (0x100), expected 0x110<br>> >>>><br>> >>>> On 5/31/2015 11:53, Jay K wrote:<br>> >>>>> John, have you tried make-dist.py?<br>> >>>>> i.e.<br>> >>> https://github.com/modula3/cm3/blob/master/scripts/python/make-dist.py<br>> >>>>><br>> >>>>> While it might not be exactly what you need, it should demonstrate the<br>> >>>>> elements.<br>> >>>>><br>> >>>>> I will try to try this all soon, really, I hope so.<br>> >>>>><br>> >>>>> It starts with a working compiler, does no in-place updates, build into<br>> >>>>> a unique directory in /tmp, and gives you .tar.gz or such at the end.<br>> >>>>> It does "min" and "all".<br>> >>>>><br>> >>>>> If you set the STAGE environment variable, it uses that instead of /tmp.<br>> >>>>> It should probably be called M3_STATE or M3_MAKEDIST_STAGE.<br>> >>>>><br>> >>>>> - Jay<br>> >>>><br>> >>>> Hi Jay,<br>> >>>> I'm getting the same error as always using make-dist script:<br>> >>>> http://leaf.dragonflybsd.org/~marino/m3d.log<br>> >>>><br>> >>>> Thanks,<br>> >>>> John<br>> ><br>> <br>> -- <br>> Rodney Bates<br>> rodney.m.bates@acm.org<br></div> </div></body>
</html>