public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] gcc: Update mpfr with patches for use in toolchain build
Date: Mon, 02 May 2022 05:33:48 +0000	[thread overview]
Message-ID: <9dc7f56b-f54d-63c9-6ac3-025ea7bbd3fc@ipfire.org> (raw)
In-Reply-To: <20220501134713.144438-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

Excellent, thank you for taking care of this.

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> - Added mpfr consolidated patches file to mpfr in gcc. mpfr is built internally for use
>    in the toolchain.
> - Confirmed working by running./make toolchain which ran successfully
>    confirmed from the _build.toolchain.log file that the patches were successfully
>    implemented for gcc pass 1, gcc pass L and gcc pass 2
> - Full toolchain build successfully completed.
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>  lfs/gcc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lfs/gcc b/lfs/gcc
> index 5ce29a13d..1d9d172c2 100644
> --- a/lfs/gcc
> +++ b/lfs/gcc
> @@ -250,6 +250,7 @@ ifeq "$(TOOLCHAIN)" "1"
>  	cd $(DIR_APP) && tar xfa $(DIR_DL)/gmp-$(GMP_VER).tar.xz
>  	cd $(DIR_APP) && mv -v gmp-$(GMP_VER) gmp
>  	cd $(DIR_APP) && tar xfa $(DIR_DL)/mpfr-$(MPFR_VER).tar.xz
> +	cd $(DIR_APP)/mpfr-$(MPFR_VER) && patch -Np1 < $(DIR_SRC)/src/patches/mpfr-4.1.0-cumulative-patches-1-to-13.patch
>  	cd $(DIR_APP) && mv -v mpfr-$(MPFR_VER) mpfr
>  	cd $(DIR_APP) && tar xfa $(DIR_DL)/mpc-$(MPC_VER).tar.gz
>  	cd $(DIR_APP) && mv -v mpc-$(MPC_VER) mpc

      reply	other threads:[~2022-05-02  5:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 13:47 Adolf Belka
2022-05-02  5:33 ` Peter Müller [this message]

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=9dc7f56b-f54d-63c9-6ac3-025ea7bbd3fc@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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