From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [pushed] doc: Remove direct reference to configure/build docs
Date: Sun, 12 Feb 2023 12:47:14 +0100 (CET) [thread overview]
Message-ID: <20230212114716.B098C33E6E@hamza.pair.com> (raw)
This has been broken for years (if not forever), both when it comes
to onlinedocs and local installations.
Pushed.
Gerald
gcc/ChangeLog:
* doc/sourcebuild.texi: Remove (broken) direct reference to
"The GNU configure and build system".
---
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
--
2.39.1
reply other threads:[~2023-02-12 11:47 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=20230212114716.B098C33E6E@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@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: 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).