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

[Olaf Wagner]

On Fri, 29 May 2015 11:35:41 -0500
"Rodney M. Bates" <rodney_bates at lcwb.coop> wrote:

> Setting INSTALL_CM3_IN_BIN=yes is what forces the premature install of cm3cg.
> I see I had encountered this problem two years ago, but then it was happening
> regardless of the value of this variable.  My fix only addresses the case when
> the variable is not set.  I naively went to extra trouble to preserve the
> existing behavior when it is set--obviously not right.
> 
> I don't see an easy way to make the variable work, as there is no
> constraint on the order that cm3 and cm3cg are built.  do-cm3-front.sh
> happens to do cm3cg first, but that is not necessarily required.
> 
> So INSTALL_CM3_IN_BIN is broken and hard to fix, if the two need
> compatible upgrades.  For now, it looks like install-cm3-compiler.sh
> is the only working way.
> 
> But maybe John and Olaf have found a different way around this.

Setting that to yes was just my suggestion after seeing in the first log
that he did install cm3 but not cm3cg. I think we should all forget about
INSTALL_CM3_IN_BIN now and leave that unset.

I still don't undertstand what he's doing differently than a simple
upgrade of the compiler based on an initial install, which does work
for AMD64_FREEBSD, as I have tested it.

I think it's the elaborate setup and build environment into which the
rather inflexible cm3 installation is forced.

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com 
               Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194