public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/uclibc: bump to 1.0.57
Date: Fri, 27 Mar 2026 11:02:37 +0100	[thread overview]
Message-ID: <20260327100237.46205-1-thomas.perale@mind.be> (raw)
In-Reply-To: <aaQ0OC8I4PAx0xZz@waldemar-brodkorb.de>

In reply of:
> Following changes made it into the release:
> 
> Joris van Rantwijk (1):
>       Fix adjtimex() with TIME64
> 
> Waldemar Brodkorb (8):
>       sys/stat.h: remove _STAT_VER/_MKNOD_VER
>       fix gettid() declaration
>       add statx syscall wrapper
>       sparc: add optimize build support for leon3
>       sparc: sync with Linux kernel definition, fixes gdb compile
>       fix compile error on earlier Kernels predating statx
>       select: fix compilation failure with very old kernel
>       bump version for 1.0.57 release
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>

Applied to 2026.02.x & 2025.02.x. Thanks

> ---
>  package/uclibc/uclibc.hash | 4 ++--
>  package/uclibc/uclibc.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/uclibc/uclibc.hash b/package/uclibc/uclibc.hash
> index 6a96e57069..e0dba1b6b4 100644
> --- a/package/uclibc/uclibc.hash
> +++ b/package/uclibc/uclibc.hash
> @@ -1,4 +1,4 @@
> -# From https://downloads.uclibc-ng.org/releases/1.0.56/uClibc-ng-1.0.56.tar.xz.sha256
> -sha256  23c9cab54c113e020fb20b9dc06be4a49560df791b78fcbc2ca899a6e8f213dd  uClibc-ng-1.0.56.tar.xz
> +# From https://downloads.uclibc-ng.org/releases/1.0.57/uClibc-ng-1.0.57.tar.xz.sha256
> +sha256  8bc734b584e23ff6ae3d0ebb4c0fb1d1d814c58c82822b93130d436afa7ace8b  uClibc-ng-1.0.57.tar.xz
>  # Locally calculated
>  sha256  ec60b993835e2c6b79e6d9226345f4e614e686eb57dc13b6420c15a33a8996e5  COPYING.LIB
> diff --git a/package/uclibc/uclibc.mk b/package/uclibc/uclibc.mk
> index 69eb73510e..0c91a176fa 100644
> --- a/package/uclibc/uclibc.mk
> +++ b/package/uclibc/uclibc.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -UCLIBC_VERSION = 1.0.56
> +UCLIBC_VERSION = 1.0.57
>  UCLIBC_SOURCE = uClibc-ng-$(UCLIBC_VERSION).tar.xz
>  UCLIBC_SITE = https://downloads.uclibc-ng.org/releases/$(UCLIBC_VERSION)
>  UCLIBC_LICENSE = LGPL-2.1+
> -- 
> 2.47.3
> 
> _______________________________________________
> 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-27 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 12:42 [Buildroot] [PATCH] package/uclibc: bump to 1.0.57 Waldemar Brodkorb
2026-03-01 18:53 ` Julien Olivain via buildroot
2026-03-02 15:58   ` Waldemar Brodkorb
2026-03-02 17:23   ` Waldemar Brodkorb
2026-03-02 21:20     ` Julien Olivain via buildroot
2026-03-02 21:40       ` Waldemar Brodkorb
2026-03-16 21:17 ` Julien Olivain via buildroot
2026-03-27 10:02 ` Thomas Perale via buildroot [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=20260327100237.46205-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=thomas.perale@mind.be \
    --cc=wbx@openadk.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