On 5/6/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
Richard Guenther wrote:> 2007-05-05 Richard Guenther <[EMAIL PROTECTED]> > > * doc/install.texi (--disable-stage1-checking): Document. > [EMAIL PROTECTED] --disable-stage1-checking > [EMAIL PROTECTED] [EMAIL PROTECTED] > +Regardless of what is specified with @samp{--enable-checking} the > +stage1 compiler is built with checking enabled. For small or slow > +systems you can disable checking for stage1 using > [EMAIL PROTECTED] Minor editing: "By default, the Stage 1 compiler is built with checking enabled, even if @option{--disable-checking} is used. If your system is too slow or too small to bootstrap the compiler with checking enabled, you can use @option{--disable-stage1-checking} to disable checking for the Stage 1 compiler." Note, in particular, that you should use @option rather than @samp. This patch is OK for 4.2 and mainline, assuming that someone verifies that the switch actually performs as advertised.
I have verified that on the branch
- without any checking option defined we build stage1 with checking=yes
and further stages with release checking
- with --enable-checking=release we build all stages with release checking
- with --disable-stage1-checking we build stage1 with --disable-checking
and further stages with release checking
- with --enable-stage1-checking=release we build stage1 with release checking
So,
2007-05-05 Richard Guenther <[EMAIL PROTECTED]>
* doc/install.texi (--enable-checking): Mention different
default for stage1.
(--enable-stage1-checking): Document.
disables1c
Description: Binary data
