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

[Jay]

Ok,caveat that I haven't tried this, could be more waste of your time,but in scripts/pkginfo.txt try moving the m3cc line down to just after cm3. This way, if the config is looking all around for it, as was mentioned and as we should avoid, it won't find it prematurely.


I was never quite sure what order to put this entry, as it has in a sense no edges to or from it in the build dependency graph. But there is the sensitivity as to when to use it, so when to ship it. Shipping after cm3 should avoid using it prematurely.

 - Jay

On May 31, 2015, at 3:15 PM, Jay <jay.krell at cornell.edu> wrote:

> I think now it might not be the problem. Could be m3cc needs to be later in pkginfo.txt. I have to try later.
> 
> - Jay
> 
> On May 31, 2015, at 10:59 AM, John Marino <adacore at marino.st> wrote:
> 
>> I removed "INSTALL_CM3_IN_BIN=yes" after reading the thread about it.
>> Should I put it back?  From the last response I'm guessing that wasn't
>> the problem.
>> 
>> John
>> 
>> 
>> On 5/31/2015 19:09, Jay K wrote:
>>> Oh probably the problem is using the backend premature actually.
>>> Darn, I can't help right now.
>>> 
>>> - Jay
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> From: jay.krell at cornell.edu
>>> To: adacore at marino.st; m3devel at elegosoft.com
>>> Date: Sun, 31 May 2015 16:45:42 +0000
>>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp
>>> (0x100), expected 0x110
>>> 
>>> Hm. Strange. I need to read more closely. I see it skipping shipping,
>>> but my read was it didn't try that.
>>> So.. with INSTALL_CM3_IN_BIN=yes?
>>> I need to try this all, and "fix" it to set that. The whole thing in
>>> m3cc/src/m3makefile is relatively
>>> new vs. when I was actively using all this. :(
>>> 
>>> - Jay
>>> 
>>> 
>>>> Date: Sun, 31 May 2015 16:57:02 +0200
>>>> From: adacore at marino.st
>>>> To: jay.krell at cornell.edu; m3devel at elegosoft.com
>>>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp
>>> (0x100), expected 0x110
>>>> 
>>>> On 5/31/2015 11:53, Jay K wrote:
>>>>> John, have you tried make-dist.py?
>>>>> i.e.
>>> https://github.com/modula3/cm3/blob/master/scripts/python/make-dist.py
>>>>> 
>>>>> While it might not be exactly what you need, it should demonstrate the
>>>>> elements.
>>>>> 
>>>>> I will try to try this all soon, really, I hope so.
>>>>> 
>>>>> It starts with a working compiler, does no in-place updates, build into
>>>>> a unique directory in /tmp, and gives you .tar.gz or such at the end.
>>>>> It does "min" and "all".
>>>>> 
>>>>> If you set the STAGE environment variable, it uses that instead of /tmp.
>>>>> It should probably be called M3_STATE or M3_MAKEDIST_STAGE.
>>>>> 
>>>>> - Jay
>>>> 
>>>> Hi Jay,
>>>> I'm getting the same error as always using make-dist script:
>>>> http://leaf.dragonflybsd.org/~marino/m3d.log
>>>> 
>>>> Thanks,
>>>> John