From: Waldemar Brodkorb <wbx@openadk.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/uclibc: bump to 1.0.57
Date: Mon, 2 Mar 2026 18:23:23 +0100 [thread overview]
Message-ID: <aaXHi1j_b4fRSI-V@waldemar-brodkorb.de> (raw)
In-Reply-To: <294c54a635aa57d40cda161b8af98f8f@free.fr>
Hi Julien,
Julien Olivain wrote,
> Hi Waldemar,
>
> Thanks for the patch.
>
> On 01/03/2026 13:42, Waldemar Brodkorb wrote:
> > 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
>
> This new uclibc version is introducing a test failure
> with zfs. See:
> https://gitlab.com/jolivain/buildroot/-/jobs/13308829775
>
> Running with the previous uclibc 1.0.56 works fine:
> https://gitlab.com/jolivain/buildroot/-/jobs/13308875027
>
> It seems related to commit:
> https://github.com/wbx-github/uclibc-ng/commit/d3a819aff25af436e22abd5ba01ff2cfc0631b32
>
> Do you have any idea which component should be fixed?
> (uclibc, zfs, or the rutime test_xzf?)
It is uclibc-ng fault. A fix and a patch v2 will follow.
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-02 17:23 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 [this message]
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
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=aaXHi1j_b4fRSI-V@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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