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

[Warwick Harvey]

Fergus wrote:
> 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.

Cool.

> 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.

Hope the relevant version got tagged to aid bootstrapping.  :-)

> ===================================================================
> RCS file: /home/mercury1/repository/mercury/configure.in,v
> retrieving revision 1.204
> diff -u -d -r1.204 configure.in
> --- configure.in 2000/05/17 12:16:06 1.204
> +++ configure.in 2000/05/24 07:17:50
> @@ -2054,8 +2055,9 @@
>  if test "$BOOTSTRAP_MC" = ""; then
>          BOOTSTRAP_MC=mmc
>  fi
> -BOOTSTRAP_MC="$BOOTSTRAP_MC $HAVE_BOXED_FLOATS --conf-low-tag-bits
> $LOW_TAG_BITS --bits-per-word $BITS_PER_WORD --bytes-per-word $BYTES_PER_WORD"
> +BOOTSTRAP_MC_FLAGS="$BOOTSTRAP_MC $HAVE_BOXED_FLOATS --conf-low-tag-bits
> $LOW_TAG_BITS --bits-per-word $BITS_PER_WORD --bytes-per-word $BYTES_PER_WORD"

Why does `BOOTSTRAP_MC_FLAGS' include `$BOOTSTRAP_MC'?


The rest looks fine, unless you want to introduce a variable for
`mmc $(BOOSTRAP_MC_FLAGS)', say `INSTALL_MC'.  (If you do that, you
could 
even wire in the installed pathname, so that you don't need to fiddle
with 
the `PATH' variable, right?)

Cheers,
Warwick
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------