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-6864] doc: Remove anachronistic note related to languages built Date: Sun, 26 Mar 2023 10:21:47 +0000 (GMT) [thread overview] Message-ID: <20230326102147.9E6CA3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:9cdbe57362e5e1c3bfdec798dfd37de2b32b24bc commit r13-6864-g9cdbe57362e5e1c3bfdec798dfd37de2b32b24bc Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun Mar 26 12:21:31 2023 +0200 doc: Remove anachronistic note related to languages built 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. Diff: --- 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
reply other threads:[~2023-03-26 10:21 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=20230326102147.9E6CA3858D28@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).