Jonathan's patch
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/604796.html
lat November made me have a look for further instances, and indeed there
was another one referring to separate tarballs (which we have not been
shipping for a fair bit).
Since the item above already refers to `gcc -v` we can simply drop the
entire list item.
Pushed.
Gerald
---
This is another instance of what ce51e8439a49 (and originally
05432288d4e5) addressed in a different part. We stopped shipping
granular tarballs years ago.
gcc/ChangeLog:
* doc/install.texi: Remove anachronistic note
related to languages built and separate source tarballs.
---
gcc/doc/install.texi | 7 -------
1 file changed, 7 deletions(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 63fc949b447..15aef1394f4 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3481,13 +3481,6 @@ 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
-Whether you enabled all languages or a subset of them. If you used a
-full distribution then this information is part of the configure
-options in the output of @samp{gcc -v}, but if you downloaded the
-``core'' compiler plus additional front ends then it isn't apparent
-which ones you built unless you tell us about it.
-
@item
If the build was for GNU/Linux, also include:
@itemize @bullet
--
2.39.2
