[m-dev.] little bootstrapping problem.

[Fergus Henderson]

On 04-Aug-1998, Tyson Dowd <trd at stimpy.cs.mu.oz.au> wrote:
> The changes I committed today to private_builtin.m won't compile without a
> new compiler compiling them -- today's compiler generates base_type_*
> for type_info/1, but there is handwritten code for type_info/1 as well.
> I've just backed it out for the moment.
> 
> What I'm think of to get around this problem is add the hand-written
> definitions for base_type_* into the runtime.  Since the runtime it is *a*
> library, the symbols won't clash with those in *the* library (linker
> will take just the first definition).  But if the library doesn't have
> the base_type_* symbols in it (stage 2), then it will get them from the
> runtime.  So stage 2 should compile OK.

I think that would work OK, so long as you make sure that the
definitions for base_type_* are in their own object module.

The alternative is to just wait until the compiler changes have been
installed on all four of our machines.  That might be a nicer solution
in the long run.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.