<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'>Given that you seem to be very quick and very patient, then yes, try that.<BR>I am trying to get back up to speed in all this, but you are way ahead of me.<BR> <BR> <BR>The actual fix in 2010 was more than Rodney described.<BR>It was removing a bunch of code.<BR> <BR> <BR>The theory is that we are still reaching around and finding the wrong cm3cg somewhere,<BR>instead of going directly to the matching one in the one place it belongs (ignoring cross build matters).<br>It isn't entirely clear though, like where would it find the wrong one.<BR>I understand how it used to go bad .<BR> <BR> <BR>see:<BR><a href="https://github.com/modula3/cm3/blob/master/m3-sys/cminstall/src/config-no-install/cm3cfg.common">https://github.com/modula3/cm3/blob/master/m3-sys/cminstall/src/config-no-install/cm3cfg.common</a><BR> <BR>I hope to get catch up soon.. :( on being away..<BR> <BR> - Jay<br><br> <BR><div>> Date: Mon, 1 Jun 2015 09:19:01 +0200<br>> From: adacore@marino.st<br>> To: jay.krell@cornell.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp (0x100), expected 0x110<br>> <br>> On 6/1/2015 09:07, John Marino wrote:<br>> > On 6/1/2015 00:51, Jay wrote:<br>> >> Ps. Update pkginfo.txt and then try make-dist.py<br>> >><br>> > <br>> > Okay, I applied this patch:<br>> > http://leaf.dragonflybsd.org/~marino/patch-scripts_pkginfo.txt<br>> > <br>> > and the same thing happened, only later:<br>> > http://leaf.dragonflybsd.org/~marino/m3e.log<br>> > <br>> <br>> <br>> Well, not the "same" thing.<br>> ${STAGE}/compiler_with_self/bin seems to be installed.<br>> <br>> I didn't change bootstrap/etc/modula3/cm3cfg.common though, it sounds<br>> like I shouldn't after all. Should I?<br>> <br>> John<br></div> </div></body>
</html>