Re: build status page problem

[Janis Johnson <janis187 at us dot ibm dot com>]

OK, I now agree that it would be a good idea to include the versions for
reports of successful GCC builds.  I'd like to request that reports
include additional relevant information, and add links to the archived
mail messages containing the reports so that the additional information
is not lost if it doesn't fit neatly into the format of the status page.

Here's how I'd like to change the Final Installation documentation for
the mainline, with similar changes to 3.0, hopefully in time for the
3.0.3 release.

--- gcc/doc/install.texi.orig	Sun Dec  9 12:13:19 2001
+++ gcc/doc/install.texi	Sun Dec  9 12:13:32 2001
@@ -1244,18 +1244,46 @@ If you built a released version of GCC t
 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-2.95/buildstat.html,,2.95}.
-If your system is not listed, send a note to
+If your system is not listed for the version of GCC that you built,
+send a note to
 @email{gcc@@gcc.gnu.org} indicating
 that you successfully built and installed GCC.
+Include the following information:
 
-Include the output from running @file{@var{srcdir}/config.guess}.  (Do
+@itemize @bullet
+@item
+Output from running @file{@var{srcdir}/config.guess}.  (Do
 not send us the @file{config.guess} file itself, just the one-line output from
-running it!)  Also specify which version you built.
-If the build was for GNU/Linux, also include the distribution name and version
-(e.g., Red Hat 7.1 or Debian 2.2.3, available from @file{/etc/issue})
-and the version of glibc you used; for RPM-based systems like Red Hat,
+running it!)
+
+@item
+The output of @samp{gcc -v} for your newly installed gcc.
+This tells us which version of GCC you built and the options you passed to
+configure.
+
+@item
+If the build was for GNU/Linux, also include:
+@itemize @bullet
+@item
+The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
+this is available from @file{/etc/issue}.
+
+@item
+The version of the Linux kernel, available from @samp{uname --version}.
+
+@item
+The version of glibc you used; for RPM-based systems like Red Hat,
 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
+@end itemize
+For other systems, you can include similar information if you think it is
+relevant.
+
+@item
+Any other information that you think would be useful to people building
+GCC on the same configuration.  The new entry in the build status list
+will include a link to the archived copy of your message.
+@end itemize
 
 We'd also like to know if the
 @ifnothtml

I can probably locate the messages reporting the existing successful
builds for GCC 3.0 and will try to add those versions to the status list
before 3.0.3 is released, when there will be a flurry of new reports.

Janis