+2002-04-30 Janis Johnson <janis187@us.ibm.com>
+
+ * doc/install.texi (Final install): Add to the list of info to include
+ in a report of a successful bootstrap, and add link to 3.1 list.
+
2002-04-30 Jakub Jelinek <jakub@redhat.com>
PR c++/6396
parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
-If you built a released version of GCC then if you don't mind, please
+If you built a released version of GCC using @samp{make bootstrap} then please
quickly review the build status page for
-@uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0} or
+@uref{http://gcc.gnu.org/gcc-3.1/buildstat.html,,3.1},
+@uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}, or
@uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
If your system is not listed for the version of GCC that you built,
send a note to
This tells us which version of GCC you built and the options you passed to
configure.
+@item
+Whether you enabled all languages or a subset of them. If you used a
+full distribution then this information is part of the configure
+options in the output of @samp{gcc -v}, but if you downloaded the
+``core'' compiler plus additional front ends then it isn't apparent
+which ones you built unless you tell us about it.
+
@item
If the build was for GNU/Linux, also include:
@itemize @bullet