[M3devel] [M3commit] CVS Update: cm3

[Olaf Wagner]

Quoting Jay <jay.krell at cornell.edu>:

>
>  > fix for old compilers that can't compile LONGINT: define   
> LongRep.T = INTEGER
>
> Is that what bootstrapping should do?
>  Automate that little patch for the first pass and undo it in the second?
>  Then always building in dependency order?
>
>
> Tonight I was trying to build from PPC_DARWIN 5.5.0.
> I figured, heck, maybe it supports LONGINT already, maybe I should just try
> building up in dependency order.
> But then I hit the problem of Compiler.i3 mismatch due to new targets.
>
>
> So...is that correct?
> Does building in dependency order predictably fail if compiler has   
> fewer targets than runtime?
> But starting with existing m3core/libm3 and first building the   
> compiler against them predictably works?

As far as I remember it has always been this way with (C)M3.
Runtime and compiler must agree wrt. target platforms.

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                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
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194