mirror of
https://github.com/Mercury-Language/mercury.git
synced 2025-12-14 13:23:53 +00:00
ef9d3eeb51
Estimated hours taken: 0.3 compiler/notes/bootstrapping.html: Fix a typo and make a few changes suggest by others.
49 lines
1.2 KiB
HTML
49 lines
1.2 KiB
HTML
|
|
<html>
|
|
<head>
|
|
<title>
|
|
Bootstrapping
|
|
</title>
|
|
</head>
|
|
|
|
<body
|
|
bgcolor="#ffffff"
|
|
text="#000000"
|
|
>
|
|
|
|
|
|
<hr>
|
|
|
|
<h2> Changes that don't bootstrap </h2>
|
|
|
|
<p>
|
|
|
|
Sometimes changes need to be made to the Mercury system that mean
|
|
previous versions of the compiler will no longer successfully compile
|
|
the new version.
|
|
<p>
|
|
|
|
Whenever anyone makes a change which prevents bootstrapping with a
|
|
previous version of the compiler, they should add a cvs tag to all the
|
|
files in the relevant directories <em>before committing</em>, and
|
|
mention this tag in the log message. The tag should be of the form
|
|
bootstrap_YYYYMMDD_<short_description_of_change>.
|
|
<p>
|
|
|
|
The rationale for the cvs tag is that it allows machines to be
|
|
bootstrapped (if they didn't manage to do it in a daily build)
|
|
by doing `cvs update -r<tag>' on the relevant build directory.
|
|
After that compiler has been installed, a `cvs update -A' will remove
|
|
the cvs sticky tags.
|
|
<p>
|
|
|
|
Optionally, a test should be added to the configuration script so
|
|
that people installing from CVS don't use an outdated compiler to
|
|
bootstrap. Practically this may be difficult to achieve in some cases.
|
|
|
|
<hr>
|
|
|
|
Last update was $Date: 1999-07-19 18:31:05 $ by $Author: trd $@cs.mu.oz.au. <br>
|
|
</body>
|
|
</html>
|