[M3devel] m3cgc1: fatal error: *** bad M3CG version stamp (0x100), expected 0x110
Jay K
jay.krell at cornell.edu
Sun May 31 19:09:24 CEST 2015
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150531/b5f2e4dd/attachment-0002.html>
More information about the M3devel
mailing list