public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Paul Kocialkowski <paulk@sys-base.io>
Cc: Thomas Perale <thomas.perale@mind.be>,
	buildroot@buildroot.org, Pedro Aguilar <paguilar@paguilar.org>
Subject: Re: [Buildroot] [PATCH] packages/libunistring: bump to version 1.4.2
Date: Fri,  6 Mar 2026 13:46:33 +0100	[thread overview]
Message-ID: <20260306124633.143362-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260225175138.2965145-1-paulk@sys-base.io>

Hi Paul,

In reply of:
> This minor release contains a fix for building with host glibc 2.43,
> which fails otherwise.
> 

I'm looking at this commit to maybe cherry-pick it for the 2025.02.x branch.
I'm running a host with glibc 2.43 and didn't manage to reproduce the build
issue. Can you point me to the commit that fixes it or an error log.

Thanks,
PERALE Thomas

> Signed-off-by: Paul Kocialkowski <paulk@sys-base.io>

> ---
>  package/libunistring/libunistring.hash | 4 ++--
>  package/libunistring/libunistring.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/libunistring/libunistring.hash b/package/libunistring/libunistring.hash
> index f86b6f94b02b..ef2f3da34147 100644
> --- a/package/libunistring/libunistring.hash
> +++ b/package/libunistring/libunistring.hash
> @@ -1,6 +1,6 @@
>  # Locally calculated after checking pgp signature
> -# https://ftp.gnu.org/gnu/libunistring/libunistring-1.4.1.tar.xz.sig
> -sha256  67d88430892527861903788868c77802a217b0959990f7449f2976126a307763  libunistring-1.4.1.tar.xz
> +# https://ftp.gnu.org/gnu/libunistring/libunistring-1.4.2.tar.xz.sig
> +sha256  5b46e74377ed7409c5b75e7a96f95377b095623b689d8522620927964a41499c  libunistring-1.4.2.tar.xz
>  # Locally calculated
>  sha256  3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986  COPYING
>  sha256  a853c2ffec17057872340eee242ae4d96cbf2b520ae27d903e1b2fef1a5f9d1c  COPYING.LIB
> diff --git a/package/libunistring/libunistring.mk b/package/libunistring/libunistring.mk
> index 1abbfde6da9e..57333a35bffc 100644
> --- a/package/libunistring/libunistring.mk
> +++ b/package/libunistring/libunistring.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -LIBUNISTRING_VERSION = 1.4.1
> +LIBUNISTRING_VERSION = 1.4.2
>  LIBUNISTRING_SITE = $(BR2_GNU_MIRROR)/libunistring
>  LIBUNISTRING_SOURCE = libunistring-$(LIBUNISTRING_VERSION).tar.xz
>  LIBUNISTRING_INSTALL_STAGING = YES
> -- 
> 2.53.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-03-06 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 17:51 [Buildroot] [PATCH] packages/libunistring: bump to version 1.4.2 Paul Kocialkowski
2026-02-26 15:45 ` Peter Korsgaard
2026-03-06 12:46 ` Thomas Perale via buildroot [this message]
2026-03-06 16:41   ` Paul Kocialkowski

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=20260306124633.143362-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=paguilar@paguilar.org \
    --cc=paulk@sys-base.io \
    --cc=thomas.perale@mind.be \
    /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