[M3devel] m3cgc1: fatal error: *** bad M3CG version stamp (0x100), expected 0x110

[Jay K]

Given that you seem to be very quick and very patient, then yes, try that.
I am trying to get back up to speed in all this, but you are way ahead of me.
 
 
The actual fix in 2010 was more than Rodney described.
It was removing a bunch of code.
 
 
The theory is that we are still reaching around and finding the wrong cm3cg somewhere,
instead of going directly to the matching one in the one place it belongs (ignoring cross build matters).
It isn't entirely clear though, like where would it find the wrong one.
I understand how it used to go bad .
 
 
see:
https://github.com/modula3/cm3/blob/master/m3-sys/cminstall/src/config-no-install/cm3cfg.common
 
I hope to get catch up soon.. :( on being away..
 
 - Jay

 
> Date: Mon, 1 Jun 2015 09:19:01 +0200
> From: adacore at marino.st
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp (0x100), expected 0x110
> 
> On 6/1/2015 09:07, John Marino wrote:
> > On 6/1/2015 00:51, Jay wrote:
> >> Ps. Update pkginfo.txt and then try make-dist.py
> >>
> > 
> > Okay, I applied this patch:
> > http://leaf.dragonflybsd.org/~marino/patch-scripts_pkginfo.txt
> > 
> > and the same thing happened, only later:
> > http://leaf.dragonflybsd.org/~marino/m3e.log
> > 
> 
> 
> Well, not the "same" thing.
> ${STAGE}/compiler_with_self/bin seems to be installed.
> 
> I didn't change bootstrap/etc/modula3/cm3cfg.common though, it sounds
> like I shouldn't after all.  Should I?
> 
> John
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150601/ce469b0c/attachment-0002.html>