From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Francis Laniel <flaniel@linux.microsoft.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: [Buildroot] [PATCH 1/9] package/uthash: new package
Date: Fri, 30 Oct 2026 16:24:26 +0100 [thread overview]
Message-ID: <20261030152434.3738285-1-angelo.compagnucci@gmail.com> (raw)
uthash is a set of C macros implementing hash tables, linked lists,
dynamic arrays and other data structures, provided as headers only.
It is needed by falcosecurity-libs, which otherwise downloads uthash.h
at build time.
Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
---
DEVELOPERS | 1 +
package/Config.in | 1 +
package/sysdig/Config.in | 2 +-
package/uthash/Config.in | 8 ++++++++
package/uthash/uthash.hash | 3 +++
package/uthash/uthash.mk | 19 +++++++++++++++++++
6 files changed, 33 insertions(+), 1 deletion(-)
create mode 100644 package/uthash/Config.in
create mode 100644 package/uthash/uthash.hash
create mode 100644 package/uthash/uthash.mk
diff --git a/DEVELOPERS b/DEVELOPERS
index b4ada4e1f9..8ca72bec84 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -261,6 +261,7 @@ F: package/sam-ba/
F: package/sshguard/
F: package/sunwait/
F: package/sysdig/
+F: package/uthash/
N: Andy Shevchenko <andy.shevchenko@gmail.com>
F: package/fb-test-app/
diff --git a/package/Config.in b/package/Config.in
index 796c4f1ad6..02932e5ac1 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -2323,6 +2323,7 @@ endif
source "package/tllist/Config.in"
source "package/tz/Config.in"
source "package/tzdata/Config.in"
+ source "package/uthash/Config.in"
source "package/uvw/Config.in"
source "package/volk/Config.in"
source "package/xapian/Config.in"
diff --git a/package/sysdig/Config.in b/package/sysdig/Config.in
index 73ac03e240..038a9734aa 100644
--- a/package/sysdig/Config.in
+++ b/package/sysdig/Config.in
@@ -24,7 +24,7 @@ config BR2_PACKAGE_SYSDIG
https://github.com/draios/sysdig/wiki
-comment "sysdig needs a glibc toolchain w/ C++, threads, wchar, gcc >= 10, dynamic library, a Linux kernel, and luajit or lua 5.1 to be built"
+comment "sysdig needs a glibc or musl toolchain w/ C++, threads, wchar, gcc >= 10, dynamic library, a Linux kernel, and luajit or lua 5.1 to be built"
depends on BR2_PACKAGE_LIBABSEIL_CPP_ARCH_SUPPORTS
depends on BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTS
depends on BR2_TOOLCHAIN_HAS_SYNC_4 || BR2_TOOLCHAIN_HAS_ATOMIC
diff --git a/package/uthash/Config.in b/package/uthash/Config.in
new file mode 100644
index 0000000000..e19c277abd
--- /dev/null
+++ b/package/uthash/Config.in
@@ -0,0 +1,8 @@
+config BR2_PACKAGE_UTHASH
+ bool "uthash"
+ help
+ uthash is a set of C macros implementing hash tables, linked
+ lists, dynamic arrays and other data structures, provided as
+ headers only.
+
+ https://troydhanson.github.io/uthash/
diff --git a/package/uthash/uthash.hash b/package/uthash/uthash.hash
new file mode 100644
index 0000000000..37a5a66aba
--- /dev/null
+++ b/package/uthash/uthash.hash
@@ -0,0 +1,3 @@
+# Locally computed
+sha256 387ba027946d7c64e9aa19cc53b2edcd714f8f9dca9fa8e3aaef17e0e8e3d736 uthash-2.4.0.tar.gz
+sha256 40f48f89e1d0095bf1c5fb4d00affd74959c3ff77463b672cf7fac547d1d6465 LICENSE
diff --git a/package/uthash/uthash.mk b/package/uthash/uthash.mk
new file mode 100644
index 0000000000..2107a90d56
--- /dev/null
+++ b/package/uthash/uthash.mk
@@ -0,0 +1,19 @@
+################################################################################
+#
+# uthash
+#
+################################################################################
+
+UTHASH_VERSION = 2.4.0
+UTHASH_SITE = $(call github,troydhanson,uthash,v$(UTHASH_VERSION))
+UTHASH_LICENSE = BSD-1-Clause
+UTHASH_LICENSE_FILES = LICENSE
+UTHASH_INSTALL_STAGING = YES
+UTHASH_INSTALL_TARGET = NO
+
+define UTHASH_INSTALL_STAGING_CMDS
+ $(INSTALL) -d $(STAGING_DIR)/usr/include
+ $(INSTALL) -m 0644 $(@D)/src/*.h $(STAGING_DIR)/usr/include
+endef
+
+$(eval $(generic-package))
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-10-30 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 15:24 Angelo Compagnucci [this message]
2026-10-30 15:24 ` [Buildroot] [PATCH 2/9] package/webrtc-audio-processing: fix build with musl Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 3/9] package/libabseil-cpp: allow building " Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 4/9] package/falcosecurity-libs: bump to version 0.21.0 Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 5/9] package/sysdig: bump to version 0.41.4 Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 6/9] package/falcosecurity-libs: convert to a virtual package Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 7/9] package/sysdig: " Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 8/9] package/falcosecurity-libs: add falcosecurity-libs-legacy Angelo Compagnucci
2026-10-30 15:24 ` [Buildroot] [PATCH 9/9] package/sysdig: add sysdig-legacy Angelo Compagnucci
2026-10-30 15:58 ` [Buildroot] [PATCH 1/9] package/uthash: new package Fiona Klute via buildroot
-- strict thread matches above, loose matches on Subject: below --
2026-10-30 13:59 Angelo Compagnucci
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=20261030152434.3738285-1-angelo.compagnucci@gmail.com \
--to=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.org \
--cc=flaniel@linux.microsoft.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