public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Janis Johnson <janis187@us.ibm.com>,
	Joe Buck <jbuck@synopsys.com>,
	gcc@gcc.gnu.org
Subject: Re: build status page problem
Date: Sun, 09 Dec 2001 12:52:00 -0000	[thread overview]
Message-ID: <20011209123440.A11359@us.ibm.com> (raw)
In-Reply-To: <200112051821.NAA26124@makai.watson.ibm.com>; from dje@watson.ibm.com on Wed, Dec 05, 2001 at 01:21:45PM -0500

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

  parent reply	other threads:[~2001-12-09 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 10:01 Joe Buck
2001-12-05 10:17 ` Janis Johnson
2001-12-05 10:22   ` David Edelsohn
2001-12-05 10:52     ` Janis Johnson
2001-12-09 12:52     ` Janis Johnson [this message]
2001-12-10  3:56       ` Gerald Pfeifer
2001-12-05 10:22   ` Joe Buck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011209123440.A11359@us.ibm.com \
    --to=janis187@us.ibm.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).