public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5954] doc: Remove direct reference to configure/build docs Date: Sun, 12 Feb 2023 11:37:14 +0000 (GMT) [thread overview] Message-ID: <20230212113714.A53343858D37@sourceware.org> (raw) https://gcc.gnu.org/g:06ca0c9abb260266b688e2c2154c72214bb47076 commit r13-5954-g06ca0c9abb260266b688e2c2154c72214bb47076 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun Feb 12 12:02:25 2023 +0100 doc: Remove direct reference to configure/build docs This has been broken for years (if not forever), both when it comes to onlinedocs and local installations. gcc/ChangeLog: * doc/sourcebuild.texi: Remove (broken) direct reference to "The GNU configure and build system". Diff: --- gcc/doc/sourcebuild.texi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index df54526464e..c348a1e47cc 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -154,8 +154,7 @@ uncompressing GCC's intermediate language in LTO object files. The build system in the top level directory, including how recursion into subdirectories works and how building runtime libraries for multilibs is handled, is documented in a separate manual, included -with GNU Binutils. @xref{Top, , GNU configure and build system, -configure, The GNU configure and build system}, for details. +with GNU Binutils. @node gcc Directory @section The @file{gcc} Subdirectory
reply other threads:[~2023-02-12 11:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230212113714.A53343858D37@sourceware.org \ --to=gerald@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).