From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Antoine Tenart <atenart@kernel.org>,
Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: Re: [Buildroot] [PATCH 01/11] package/libselinux: fix build issues caused by 3.8.1 bump
Date: Mon, 15 Sep 2025 00:28:28 +0200 [thread overview]
Message-ID: <14e1befe002ce593820b4bc1dd63d04e@free.fr> (raw)
In-Reply-To: <20250909120822.1069595-2-thomas.petazzoni@bootlin.com>
On 09/09/2025 14:08, Thomas Petazzoni via buildroot wrote:
> Since the bump to version 3.8.1 in commit
> 1ae3ad4e878e1f4217ba3276ff0c9e584234afa4, libselinux fails to build
> with at least
>
> - Musl configurations
> - RISC-V 32-bit configurations
> - OpenRISC configurations
>
> These build failures are due to additional checks on the size of some
> data structures:
>
> matchpathcon.c:270:47: error: '__ino_t' undeclared here (not in a
> function); did you mean 'ino_t'?
> 270 | static_assert(sizeof(unsigned long) == sizeof(__ino_t), "inode
> size mismatch");
> | ^~~~~~~
> | ino_t
> matchpathcon.c:270:15: error: expression in static assertion is not an
> integer
> 270 | static_assert(sizeof(unsigned long) == sizeof(__ino_t), "inode
> size mismatch");
> | ^~~~~~
>
> These issues have been fixed in follow-up upstream commits, which we
> backport.
>
> Fixes:
>
>
> https://autobuild.buildroot.net/results/00a1ab30cc6b7af503aa96384ba4c4444c217401/
> (musl)
>
> https://autobuild.buildroot.net/results/c8321be687201937bd5eb48b31dfabac12f4e9ea/
> (glibc or1k)
>
> https://autobuild.buildroot.net/results/7b94f44282582d5994f40a741cc0c38bd68b53bd/
> (risc-v 32-bit)
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
I applied the full series to master, thanks.
While reviewing, I found one corner case build failure with libselinux
3.9
on x86_64 uclibc. See:
https://gitlab.com/jolivain/buildroot/-/jobs/11350151899
It seems to be a followup issue related to the one fixed in this patch.
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-09-14 22:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 12:08 [Buildroot] [PATCH 00/11] SELinux fixes and updates Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 01/11] package/libselinux: fix build issues caused by 3.8.1 bump Thomas Petazzoni via buildroot
2025-09-14 22:28 ` Julien Olivain via buildroot [this message]
2025-09-15 6:06 ` Thomas Petazzoni via buildroot
2025-09-19 18:42 ` Waldemar Brodkorb
2025-09-19 19:00 ` Thomas Petazzoni via buildroot
2025-09-20 6:07 ` Waldemar Brodkorb
2025-09-20 8:45 ` Thomas Petazzoni via buildroot
2025-09-19 12:59 ` Thomas Perale via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 02/11] package/libsemanage: fix build issue due to basename() Thomas Petazzoni via buildroot
2025-09-19 12:56 ` Thomas Perale via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 03/11] package/policycoreutils: fix build with musl due to getpass() Thomas Petazzoni via buildroot
2025-09-19 12:56 ` Thomas Perale via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 04/11] package/libselinux: bump version to 3.9 Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 05/11] package/checkpolicy: bump to version 3.9 Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 06/11] package/libsemanage: " Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 07/11] package/libsepol: " Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 08/11] package/policycoreutils: " Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 09/11] package/restorecond: " Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 10/11] package/selinux-python: " Thomas Petazzoni via buildroot
2025-09-09 12:08 ` [Buildroot] [PATCH 11/11] package/semodule-utils: " Thomas Petazzoni 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=14e1befe002ce593820b4bc1dd63d04e@free.fr \
--to=buildroot@buildroot.org \
--cc=atenart@kernel.org \
--cc=ju.o@free.fr \
--cc=marcus.folkesson@gmail.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.