public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org,
	"José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/zfs: add patch to fix build with uclibc >= 1.0.57
Date: Mon, 16 Mar 2026 21:59:26 +0100	[thread overview]
Message-ID: <7fb4a892fa061d8da919446f9c4d5352@free.fr> (raw)
In-Reply-To: <20260316201420.798780-1-ju.o@free.fr>

On 16/03/2026 21:14, Julien Olivain via buildroot wrote:
> uclibc 1.0.57 added a statx() syscall wrapper in upstream commit [1].
> 
> zfs fail to build with uclibc 1.0.57 (not yet in Buildroot), because:
> 1. uclibc <fcntl.h> internally includes <sys/stat.h>, and
> 2. a zfs test redefines a statx() wrapper with a slightly different
>    prototype.
> 
> In that case, zfs fails to compile with error:
> 
>     tests/zfs-tests/cmd/statx.c:58:1: error: conflicting types for 
> 'statx'; have 'int(int,  const char *, int,  unsigned int,  void *)'
> 
> Issue has been reported upstream at [2].
> 
> This commit adds a package patch to fix that issue.
> 
> [1] 
> https://github.com/wbx-github/uclibc-ng/commit/d3a819aff25af436e22abd5ba01ff2cfc0631b32
> [2] https://github.com/openzfs/zfs/pull/18316
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>

Applied to master.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-03-16 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 20:14 [Buildroot] [PATCH 1/1] package/zfs: add patch to fix build with uclibc >= 1.0.57 Julien Olivain via buildroot
2026-03-16 20:59 ` Julien Olivain via buildroot [this message]
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=7fb4a892fa061d8da919446f9c4d5352@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=salvador.joseluis@gmail.com \
    /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