public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benson Muite <benson_muite@emailplus.org>
To: gcc-patches@gcc.gnu.org
Subject: [ping][PATCH 1/1] docs: Add link to gmplib.org
Date: Wed, 11 Jan 2023 17:57:09 +0300	[thread overview]
Message-ID: <10167ba9-0bae-d365-b5d1-3bfd4d299213@emailplus.org> (raw)
In-Reply-To: <20230105033853.7111-2-benson_muite@emailplus.org>

Improvement to documentation from a new contributor without commit rights.

On 1/5/23 06:38, Benson Muite wrote:
> Link is missing from install documentation
> 
> Signed-off-by: Benson Muite <benson_muite@emailplus.org>
> ---
>  gcc/doc/install.texi | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
> index ccc8d15fd08..18e8709a169 100644
> --- a/gcc/doc/install.texi
> +++ b/gcc/doc/install.texi
> @@ -396,7 +396,8 @@ install the libraries.
>  @table @asis
>  @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
>  
> -Necessary to build GCC@.  If a GMP source distribution is found in a
> +Necessary to build GCC@.  It can be downloaded from
> +@uref{https://gmplib.org/}.  If a GMP source distribution is found in a
>  subdirectory of your GCC sources named @file{gmp}, it will be built
>  together with GCC.  Alternatively, if GMP is already installed but it
>  is not in your library search path, you will have to configure with the


  reply	other threads:[~2023-01-11 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  5:32 [PATCH] " Benson Muite
2023-01-05  3:38 ` [PATCH 0/1] Update installation docs with gmplib link Benson Muite
2023-01-05  3:38   ` [PATCH 1/1] Add link to gmplib.org Benson Muite
2023-01-11 14:57     ` Benson Muite [this message]
2023-03-07 23:42       ` [ping][PATCH 1/1] docs: " Sandra Loosemore
2023-03-08  6:26         ` Benson Muite

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=10167ba9-0bae-d365-b5d1-3bfd4d299213@emailplus.org \
    --to=benson_muite@emailplus.org \
    --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).