[m-dev.] for review: use new compiler when building library grades

Tyson Dowd trd at cs.mu.OZ.AU
Mon May 29 14:25:36 AEST 2000


On 24-May-2000, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> Peter Ross volunteered to test & review this.
> 
> ----------
> 
> Estimated hours taken: 0.75
> 
> Fix a problem bootstrapping introduced by the MLDS back-end changes.
> Also reduce the vulnerability of the installation process to these
> kind of bootstrapping problems, by using the newly installed compiler
> to build the library grades.
> 
> configure.in:
> 	When testing whether the installed compiler is sufficiently up-to-date,
> 	use `--high-level-code', since the installation process now requires
> 	the compiler to generate .dep files that support --high-level-code.

This means you now have to install the high level code grade in order to
bootstrap, but you never use it for anything except passing this test.

In theory it would be better to just test that the compiler accepts the
--high-level-code option, not that you can actually link something
with it.

Using --high-level-code --compile-to-c would probably be enough.

I don't know whether this is worth fixing, but it just bit me so it
might be worth people knowing about.

-- 
       Tyson Dowd           # 
                            #  Surreal humour isn't everyone's cup of fur.
     trd at cs.mu.oz.au        # 
http://www.cs.mu.oz.au/~trd #
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------



More information about the developers mailing list