[M3devel] bootstrapping problems

Jay K jay.krell at cornell.edu
Mon Feb 14 03:16:48 CET 2011


/home/mika/cm3/cm3/m3-sys/m3cc/AMD64_LINUX/cm3cg

That is the problem.
For a long time, my config file were willing to run that.
Instead of cm3cg in $PATH or cm3cg next to cm3.
It bit me a bit too so I stopped doing it that way.

The instructions are ok. Certainly the skipgcc.
Nocleangcc depends on underlying correct incrementality, so might be a bit fragile.
The backend has no need or obligation to be forward or backward compatible
with any cm3/m3front. It need only be compatible with the one it goes with.

The upgrading of cm3 and cm3cg is carefully coordinated to avoid any mismatch.
Whenever the uprading has gone wrong, it has been fixed. Not any sort
of compatibility restored.

Granted, we could better use the version declaration and error right away clearly.
I can make a change there.

 - Jay
> To: m3devel at elegosoft.com
> Date: Sun, 13 Feb 2011 15:16:26 -0800
> From: mika at async.caltech.edu
> Subject: Re: [M3devel] bootstrapping problems
> 
> I should probably not have "nocleangcc" and "skipgcc" in there huh...
> 
> still a bit weird that the back-end isn't backward compatible?
> 
>     Mika
> 
> Mika Nystrom writes:
> >Jay sent me the following instructions for bootstrapping a while back:
> >
> >./upgrade.py nocleangcc && 
> >    ./do-cm3-all.py realclean skipgcc && 
> >    ./do-cm3-all.py buildship skipgcc
> >
> >It seems reasonable enough for me. 
> >
> >I unpacked the REL distribution, checked everything out, etc.
> >
> >However something is very wrong.  The newer back-end does not seem
> >compatible with the old m3front (not even backward-compatible), and it's
> >getting called at the wrong time:
> >
> >ignoring ../src/m3overrides
> >
> >rm .M3SHIP
> >rm .M3OVERRIDES
> >rm .generic.tmp
> >rm .generic.tmp
> >inhale libsysutils.m3x
> >inhale /usr/local/cm3/pkg/m3core/AMD64_LINUX/libm3core.a
> >inhale /usr/local/cm3/pkg/libm3/AMD64_LINUX/libm3.a
> >
> >new source -> compiling EnvUtils.i3
> >m3front ../src/EnvUtils.i3 -w1
> >/home/mika/cm3/cm3/m3-sys/m3cc/AMD64_LINUX/cm3cg -gstabs+ -m64 -fPIC -mno-alig
> >n-double -funwind-tables -quiet -fno-reorder-blocks EnvUtils.ic -o EnvUtils.is
> >cm3cg: fatal error:  *** illegal type: 0x17, at m3cg_lineno 4
> >compilation terminated.
> >  m3_backend => 1
> >m3cc (aka cm3cg) failed compiling: EnvUtils.ic
> >rm EnvUtils.is
> >
> >Why is it calling the new back end?  This is the very first thing it does (it 
> >hasn't cleaned m3cc for some reason).
> >
> >The new back end doesn't like the output of the old compiler:
> >
> >(119)ukdsl204:~/cm3/cm3/m3-libs/sysutils/AMD64_LINUX>/home/mika/cm3/cm3/m3-sys
> >/m3cc/AMD64_LINUX/cm3cg -gstabs+ -m64 -fPIC -mno-align-double -funwind-tables 
> >-quiet -fno-reorder-blocks EnvUtils.ic -o EnvUtils.is
> >cm3cg: fatal error:  *** illegal type: 0x17, at m3cg_lineno 4
> >compilation terminated.
> >
> >But the old one in /usr/local/cm3/bin likes it just fine...
> >
> >(120)ukdsl204:~/cm3/cm3/m3-libs/sysutils/AMD64_LINUX>cm3cg -gstabs+ -m64 -fPIC
> > -mno-align-double -funwind-tables -quiet -fno-reorder-blocks EnvUtils.ic -o E
> >nvUtils.is
> >(121)ukdsl204:~/cm3/cm3/m3-libs/sysutils/AMD64_LINUX>
> >
> >Is something going wrong with the bootstrapping process?  I'm going to
> >try to delete the newer back end and see if that fixes it.
> >
> >     Mika
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20110214/9c1d9803/attachment-0002.html>


More information about the M3devel mailing list