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

[Jay K]

make-dist makes everything.
 

It makes a "min" distribution and an "all" distribution.
Hopefully you can read it through it makes semi-reasonable sense.
 

This is all my doing -- which is to say, I quite like it,
but not necessarily anyone else.
 

min as I recall, is just the compiler: cm3, cm3cg, mklib, config, m3core, libm3 
 (mklib is only for NT386 target, but it is small and innocuous)
 

all is everything, including min
 

I don't like the confusion and purported complexity of breaking
things down into several medium sized packages, with dependencies.

 
I want more of a "one stop shop", granted, a big one, that
gives everyone stuff they won't use.
 
 
 
But I compromised and it makes to things.

 
 
It makes roughly speaking .tar.gz files.
Or .zips for some targets.
Or compresed tar, depending on what compressor it can find, and bundles
them into .deb files. But .deb files are little more than .tar.gz or .tar.bz2 or .tar.xz
 
 
upgrade.sh also builds everything

 
When I wrote it to upgrade.py I missed that significant aspect, and it only builds the compiler.
Perhaps I should rename it to upgrade-min.py and then have upgrade-all.py.
 

You can mimic upgrade.sh with ugprade.py && do-cm3-all.py realclean skipgcc && do-cm3-all.py buildship
(skipgcc is just an optimization to avoid some duplicate work)
 

I never use any of the .sh files.
I found them to hard to understand and not portable enough.
i.e. I'd rather install Python on Windows than Cygwin.
I suspect Bourne shell is just not worth learning to program in.
 

I had rewritten them in .cmd for Windows, but wanted one set of scripts.

 
cvs is pretty awful.
I'm still more productive in it than git, but I expect that will change.
But ok. cvsup can work. The error is for a trivial thing.

 - Jay



 
> Date: Mon, 1 Jun 2015 10:25:11 +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 10:15, Jay K wrote:
> > This is very good progress.
> > Thank you for your speed and patience.
> >  
> >  
> > And the error is kind of minor and uninteresting. Yes, I understand, it
> > is fatal. Everything should just work to completion.
> >  
> >  
> > See IsDarwin here:
> >  
> >  
> >  https://github.com/modula3/cm3/blob/master/m3-sys/cminstall/src/config-no-install/cm3cfg.common 
> >  
> >  
> > cvsup is fiddling around how to use zlib.
> > See here:
> > https://github.com/modula3/cm3/blob/master/m3-tools/cvsup/suplib/src/m3makefile
> >  
> >  
> > and surely cvsup isn't interesting any more? Who is using cvs?
> 
> NetBSD and OpenBSD for starters.
> 
> 
> 
> > You can delete m3-tools/cvsup.
> > or change the scripts to skip it
> > or update cm3cfg.common to be more up to date.
> 
> I'd like to keep it, it's the best source for cvsup.
> 
> I thought make-dist.py was just going to bootstrap (e.g. minimal
> required).  Is it actually building everything?
> 
> 
> I was intending to run do-cm3-min.sh buildship, do-cm3-std.sh buildship,
> do-cm3-caltech-parser.sh buildship after make-dist.py completed.
> 
> John
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150601/f81304c7/attachment-0001.html>