From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Julien Olivain <ju.o@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Petr Vorel <petr.vorel@gmail.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: [Buildroot] [PATCH 2/2] package/ltp-testsuite: bump version to 20260130
Date: Tue, 3 Feb 2026 23:44:13 +0100 [thread overview]
Message-ID: <20260203224414.192218-2-petr.vorel@gmail.com> (raw)
In-Reply-To: <20260203224414.192218-1-petr.vorel@gmail.com>
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
Hi all,
there are sill some failures:
* br-arm-basic [28/35]: FAILED
fcntl31.c:122:22: error: ‘F_GETOWN_EX’ undeclared (first use in this function); did you mean ‘F_GETOWN’?
122 | TEST(fcntl(test_fd, F_GETOWN_EX, &orig_own_ex));
fcntl31.c:182:22: error: ‘F_SETOWN_EX’ undeclared (first use in this function); did you mean ‘F_SETOWN’?
TEST(fcntl(test_fd, F_SETOWN_EX, &orig_own_ex));
The config have:
BR2_TOOLCHAIN_EXTERNAL_HEADERS_5_9=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC=y
I was thinking about something like:
depends on !BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_HEADERS_AT_LEAST_?_?
but it's not about kernel headers (include/uapi/asm-generic/fcntl.h
contains both F_GETOWN_EX and F_SETOWN_EX in 2.6), but more about the
fact that uClibc-ng version in the toolchain is 1.0.36, but <fcntl.h>
requires newer uClibc-ng, as it was added in v1.0.45:
98576ab8d ("fcntl.h: declare f_owner_ex for all architectures")
How to express this dependency in Buildroot?
Also, I could fix it in LTP upstream if you think 1.0.36 is still new
enough and there are users who actually use LTP with these older
toolchains.
Kind regards,
Petr
package/ltp-testsuite/ltp-testsuite.hash | 4 ++--
package/ltp-testsuite/ltp-testsuite.mk | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/ltp-testsuite/ltp-testsuite.hash b/package/ltp-testsuite/ltp-testsuite.hash
index b96e1f46fa..e1861ae4e4 100644
--- a/package/ltp-testsuite/ltp-testsuite.hash
+++ b/package/ltp-testsuite/ltp-testsuite.hash
@@ -1,4 +1,4 @@
-# From: https://github.com/linux-test-project/ltp/releases/download/20250930/ltp-full-20250930.tar.xz.sha256
-sha256 048fa4d69ddbe8a94aa15da9bdc85713ab07a0abbc3de2b8bdd9757644aef1e4 ltp-full-20250930.tar.xz
+# From: https://github.com/linux-test-project/ltp/releases/download/20260130/ltp-full-20260130.tar.xz.sha256
+sha256 5effc9d3eb3f5cd45d47e8ac3d78f59cb8f3f73c8598a2f182ef5b40ddfff311 ltp-full-20260130.tar.xz
# Locally computed
sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643 COPYING
diff --git a/package/ltp-testsuite/ltp-testsuite.mk b/package/ltp-testsuite/ltp-testsuite.mk
index 12db8f2d3b..2e4767b1a5 100644
--- a/package/ltp-testsuite/ltp-testsuite.mk
+++ b/package/ltp-testsuite/ltp-testsuite.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LTP_TESTSUITE_VERSION = 20250930
+LTP_TESTSUITE_VERSION = 20260130
LTP_TESTSUITE_SOURCE = ltp-full-$(LTP_TESTSUITE_VERSION).tar.xz
LTP_TESTSUITE_SITE = https://github.com/linux-test-project/ltp/releases/download/$(LTP_TESTSUITE_VERSION)
--
2.51.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-03 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 22:44 [Buildroot] [PATCH 1/2] package/ltp-testsuite: Always require host-pkgconf Petr Vorel
2026-02-03 22:44 ` Petr Vorel [this message]
2026-03-16 8:07 ` [Buildroot] [PATCH 2/2] package/ltp-testsuite: bump version to 20260130 Petr Vorel
2026-03-16 8:09 ` [Buildroot] [PATCH 1/2] package/ltp-testsuite: Always require host-pkgconf Petr Vorel
2026-03-30 19:52 ` Julien Olivain 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=20260203224414.192218-2-petr.vorel@gmail.com \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@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