From patchwork Sun Dec 17 01:21:44 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerald Pfeifer X-Patchwork-Id: 82322 Return-Path: X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id D715338582A7 for ; Sun, 17 Dec 2023 01:22:10 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id 1190B3858D28 for ; Sun, 17 Dec 2023 01:21:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1190B3858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pfeifer.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 1190B3858D28 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=209.68.5.143 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702776113; cv=none; b=ru5fh4uZGKhRl+hxTIP3SlXrUpPNwqvYTmNfttuwJVl/UD9SYe/HUYtaIWjbMIDfptQw2aD1RuYj+TzI/Ybw2ESOfvOgvnIQxc28YZQ39GhGodsh9YCcGIeWcaD5ZlRl+B2NVKpNVziIhFH6Wk27Dc7trVv8LsFkdRNY0S52Z+0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702776113; c=relaxed/simple; bh=aMz1lQbtbBayGfx82lKWHlIEQv90M/ei9vYxFZ+1rQo=; h=Date:From:To:Subject:MIME-Version:Message-Id; b=wVX/C+Thjkr8fPUQgFb+spJ0SS0tnsw1fRv6ATHJeSHdggUB3899DwbRjxNWC7+zsGP2U4g6fE+6c0ofdBagfPfIHPvWNvXOF1YgZ9xHUbHo19ZyZ7T83G9UJTWS3FDmSO7F8C5M3bzpljz2y2s/9FDfogC0EdyIOuudeO/VrI4= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id AA1DE33E9F; Sat, 16 Dec 2023 20:21:49 -0500 (EST) Received: from [192.168.1.63] (unknown [103.162.115.197]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id 4C50F33EAE; Sat, 16 Dec 2023 20:21:47 -0500 (EST) Date: Sun, 17 Dec 2023 09:21:44 +0800 (WITA) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org cc: Thomas Schwinge Subject: [pushed] doc: Remove references to buildstat.html MIME-Version: 1.0 X-Scanned-By: mailmunge 3.11 on 209.68.5.143 Message-Id: <20231217012149.AA1DE33E9F@hamza.pair.com> X-Spam-Status: No, score=-10.7 required=5.0 tests=BAYES_00, GIT_PATCH_0, KAM_DMARC_STATUS, KAM_SHORT, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org After addressing the references to the stale information Thomas pointed out on our web pages, this addresses our documentation. (I can't believe we still had a reference to SuSE, more than twenty years after the name changed to SUSE.) Gerald gcc: PR other/69374 * doc/install.texi (Installing GCC): Remove reference to buildstat.html. (Testing): Ditto. (Final install): Remove section on submitting information for buildstat.html. Adjust the request for feedback. --- gcc/doc/install.texi | 53 +------------------------------------------- 1 file changed, 1 insertion(+), 52 deletions(-) diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index fffad700af7..5ec81098d47 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -158,10 +158,6 @@ package-specific installation instructions. We recommend you browse the entire generic installation instructions before you proceed. -Lists of successful builds for released versions of GCC are -available at @uref{https://gcc.gnu.org/buildstat.html}. -These lists are updated as new information becomes available. - The installation procedure itself is broken into five steps. @ifinfo @@ -3286,9 +3282,6 @@ Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the @uref{https://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}. -Some of these archived results are linked from the build status lists -at @uref{https://gcc.gnu.org/buildstat.html}, although not everyone who -reports a successful build runs the testsuites and submits the results. This step is optional and may require you to download additional software, but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC@. @@ -3593,51 +3586,7 @@ Alternatively, there are prebuilt online versions of the manuals for released versions of GCC on @uref{https://gcc.gnu.org/onlinedocs/,,the GCC web site}. -If you are bootstrapping a released version of GCC then please -quickly review the build status page for your release, available from -@uref{https://gcc.gnu.org/buildstat.html}. -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: - -@itemize @bullet -@item -Output from running @file{@var{srcdir}/config.guess}. Do not send -that file itself, just the one-line output from running it. - -@item -The output of @samp{gcc -v} for your newly installed @command{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 information should be available from @file{/etc/issue}. - -@item -The version of the Linux kernel, available from @samp{uname --version} -or @samp{uname -a}. - -@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 +If you built GCC yourself we would like to know if the @ifnothtml @ref{Specific, host/target specific installation notes} @end ifnothtml