public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: development@lists.ipfire.org
Subject: Re: [PATCH] mpfr: Update to version 4.2.2
Date: Fri, 21 Mar 2025 15:15:56 +0000	[thread overview]
Message-ID: <72C4A248-0317-4ED4-AB56-78DBA35F6613@ipfire.org> (raw)
In-Reply-To: <20250321133045.3267597-1-adolf.belka@ipfire.org>

Thank you.

I also updated the statically linked version in GCC:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=ba4bc8da4eec7fdb43d8c0b444aec8b2343deb86

This should not be shipped, but I think we should have the same version everywhere...

-Michael

> On 21 Mar 2025, at 13:30, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> - Update from version 4.2.1 to 4.2.2
> - Update of rootfile
> - Changelog
>    4.2.2
> - In order to resolve a portability issue with the _Float128 fallback to
>  __float128 for binary128 support (e.g. with Clang and glibc 2.41), the
>  prototypes of the corresponding conversion functions had to be changed,
>  with _Float128 replaced by mpfr_float128, where mpfr_float128 is a macro
>  defined as _Float128 by default. This changes neither the ABI nor the API
>  (except that the end user of MPFR would need to define mpfr_float128 as
>  the actual type for the binary128 format if this is not the standard
>  _Float128 type).
> - Other bug fixes (see <https://www.mpfr.org/mpfr-4.2.1/#fixed> and/or the
>  ChangeLog file). In particular, the formatted output functions behaved
>  incorrectly with %c on the value 0; such a use is uncommon, but this bug
>  may have security implications.
> - Improved MPFR manual.
> - Detect the use of GMP's buggy vsnprintf replacement at configure time.
>  With it, the tests of "%a" will be disabled to avoid an assertion failure
>  in the MPFR testsuite. A warning will be displayed in the configure output
>  in such a case.
> Also, note that due to new tests related to the fix of the formatted
>  output functions with %c on the value 0, failures in the tfprintf and
>  tsprintf tests may be observed if GMP has been built with its vsnprintf
>  replacement (i.e. if GMP detected at configure time that the vsnprintf
>  function from the C library is buggy/non-conforming). This is due to a
>  bug in the vsnprintf replacement from GMP 6.3.0 (official tarball) and
>  below. This could be observed on MS Windows and OpenBSD. To get rid of
>  these failures, either use a fixed version (recommended!) or build the
>  MPFR tests with the MPFR_TESTS_SKIP_CHECK_NULL macro defined.
>  See the INSTALL file for other details.
> 
> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
> ---
> config/rootfiles/common/mpfr | 2 +-
> lfs/mpfr                     | 7 +++----
> 2 files changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/config/rootfiles/common/mpfr b/config/rootfiles/common/mpfr
> index e3cf8d2da..1d55558a4 100644
> --- a/config/rootfiles/common/mpfr
> +++ b/config/rootfiles/common/mpfr
> @@ -4,7 +4,7 @@
> #usr/lib/libmpfr.la
> #usr/lib/libmpfr.so
> usr/lib/libmpfr.so.6
> -usr/lib/libmpfr.so.6.2.1
> +usr/lib/libmpfr.so.6.2.2
> #usr/lib/pkgconfig/mpfr.pc
> #usr/share/doc/mpfr
> #usr/share/doc/mpfr/AUTHORS
> diff --git a/lfs/mpfr b/lfs/mpfr
> index 018bc39d7..30f64d82d 100644
> --- a/lfs/mpfr
> +++ b/lfs/mpfr
> @@ -1,7 +1,7 @@
> ###############################################################################
> #                                                                             #
> # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2023  IPFire Team  <info@ipfire.org>                     #
> +# Copyright (C) 2007-2025  IPFire Team  <info@ipfire.org>                     #
> #                                                                             #
> # This program is free software: you can redistribute it and/or modify        #
> # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 4.2.1
> +VER        = 4.2.2
> 
> THISAPP    = mpfr-$(VER)
> DL_FILE    = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_BLAKE2 = ad69f53bc910294647523e7613b18a683f1d0f3dd994168ab2a46b66d0371ffa9b8e7cb59495f898470aea69d343e83fc722f11babe4af7b3a12665a1e65860c
> +$(DL_FILE)_BLAKE2 = 6bbf5658e70fbb673a3b65246a6bac708d1571aa6943c6742efd92f468ac71e6f0fe351b757f7133440ea312d9a5fc3549acd89d54f4d975c58bdc204d7b21ec
> 
> install : $(TARGET)
> 
> @@ -70,7 +70,6 @@ $(subst %,%_BLAKE2,$(objects)) :
> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> @$(PREBUILD)
> @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
> -# cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/mpfr-4.2.1-cumulative-patches-1-to-x.patch
> cd $(DIR_APP) && $(CONFIGURE_ARGS) ./configure \
> --prefix=/usr \
> --enable-thread-safe
> -- 
> 2.49.0
> 
> 



      reply	other threads:[~2025-03-21 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 13:30 Adolf Belka
2025-03-21 15:15 ` Michael Tremer [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=72C4A248-0317-4ED4-AB56-78DBA35F6613@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=adolf.belka@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