From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH v2] doc: Remove outdated reference to "core" and front-end downloads
Date: Wed, 9 Nov 2022 22:12:05 +0000 [thread overview]
Message-ID: <20221109221205.61966-1-jwakely@redhat.com> (raw)
In-Reply-To: <20221101135941.444266-1-jwakely@redhat.com>
Patch rebased on the new doc format. I haven't tested building the docs
this way, but this is just plain text here.
OK for trunk?
-- >8 --
gcc/ChangeLog:
* doc/install/testing.rst: Remove anachronism about separate
source tarballs.
---
gcc/doc/install/testing.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/gcc/doc/install/testing.rst b/gcc/doc/install/testing.rst
index 4ae17688440..58d93cc4378 100644
--- a/gcc/doc/install/testing.rst
+++ b/gcc/doc/install/testing.rst
@@ -22,9 +22,7 @@ but it can give you confidence in your new GCC installation or point out
problems before you install and start using your new GCC.
First, you must have :ref:`downloaded the testsuites <downloading-the-source>`.
-These are part of the full distribution, but if you downloaded the
-'core' compiler plus any front ends, you must download the testsuites
-separately.
+These are included in the source tarball.
Second, you must have the testing tools installed. This includes
`DejaGnu <https://www.gnu.org/software/dejagnu/>`_, Tcl, and Expect;
--
2.38.1
next prev parent reply other threads:[~2022-11-09 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:59 [PATCH] " Jonathan Wakely
2022-11-09 22:12 ` Jonathan Wakely [this message]
2022-11-13 1:27 ` [PATCH v2] " Jeff Law
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=20221109221205.61966-1-jwakely@redhat.com \
--to=jwakely@redhat.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).