From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15922 invoked by alias); 9 Dec 2001 20:31:59 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 15870 invoked from network); 9 Dec 2001 20:31:54 -0000 Received: from unknown (HELO e31.co.us.ibm.com) (32.97.110.129) by sources.redhat.com with SMTP; 9 Dec 2001 20:31:54 -0000 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.99.140.24]) by e31.co.us.ibm.com (8.9.3/8.9.3) with ESMTP id PAA38644; Sun, 9 Dec 2001 15:29:02 -0500 Received: from gateway.beaverton.ibm.com (gateway.beaverton.ibm.com [138.95.180.1]) by westrelay03.boulder.ibm.com (8.11.1m3/NCO v5.01) with ESMTP id fB9KVne38880; Sun, 9 Dec 2001 13:31:49 -0700 Received: from eng2.beaverton.ibm.com (eng2.beaverton.ibm.com [138.95.200.91]) by gateway.beaverton.ibm.com (8.10.0.Beta10/8.11.2) with ESMTP id fB9KVYV02162; Sun, 9 Dec 2001 12:31:34 -0800 (PST) Received: from unknown.host (lig32-224-94-50.us.lig-dial.ibm.com [32.224.94.50]) by eng2.beaverton.ibm.com (8.10.0.Beta10/8.8.5/token.aware-1.2) with ESMTP id fB9KVTQ13112; Sun, 9 Dec 2001 12:31:29 -0800 (PST) Received: (from janis@localhost) by unknown.host (8.9.3/8.9.3) id MAA11369; Sun, 9 Dec 2001 12:34:40 -0800 Date: Sun, 09 Dec 2001 12:52:00 -0000 From: Janis Johnson To: David Edelsohn Cc: Janis Johnson , Joe Buck , gcc@gcc.gnu.org Subject: Re: build status page problem Message-ID: <20011209123440.A11359@us.ibm.com> References: <200112051821.NAA26124@makai.watson.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112051821.NAA26124@makai.watson.ibm.com>; from dje@watson.ibm.com on Wed, Dec 05, 2001 at 01:21:45PM -0500 X-SW-Source: 2001-12/txt/msg00443.txt.bz2 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