From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH 2/4] package/wireplumber: mark broken on uClibc
Date: Tue, 14 Apr 2026 18:20:26 +0200 [thread overview]
Message-ID: <20260414162028.2141018-2-bernd@kuhls.net> (raw)
In-Reply-To: <20260414162028.2141018-1-bernd@kuhls.net>
../lib/wp/log.c:780:49: error: implicit declaration of function ‘gettid’;
did you mean ‘getgid’? [-Wimplicit-function-declaration]
780 | g_autofree gchar *tid = g_strdup_printf("%d", gettid());
The problem was hidden by pipewire being broken with uClibc since at
least Sep 2024: https://autobuild.buildroot.net/results/ee5/ee50c8331946814c2fecb0ca56ca51c1bb0bc551/
Pipewire was bumped from 0.3.81 to 1.2.2 in Aug 2024 with buildroot commit
93b72692c36f8357e867650f4b8fac91dff375f5 which afaics caused all uClibc
builds to fail due to missing tss_t() whose usage was added to pipewire in
version 1.1.81 (https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/
de0db48f17aa391917ff5b430b7b9fe1dac443fe) and later removed with https://
gitlab.freedesktop.org/pipewire/pipewire/-/commit/
9c19284f7f062a50e059b0593068429b345acf34 in version 1.3.81.
In wireplumber the relevant part of code with gettid() was added in
version 0.5.9. Buildroot bumped wireplumber from 0.5.5 directly to 0.5.10
with commit c42b26bb471a260e2bb3da7988af77f78b2b4280.
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
package/wireplumber/Config.in | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/wireplumber/Config.in b/package/wireplumber/Config.in
index 6528a2e102..e43f1ed52a 100644
--- a/package/wireplumber/Config.in
+++ b/package/wireplumber/Config.in
@@ -4,6 +4,7 @@ config BR2_PACKAGE_WIREPLUMBER
depends on BR2_PACKAGE_LUA_5_3 || BR2_PACKAGE_LUA_5_4
depends on BR2_USE_WCHAR # libglib2
depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2
+ depends on !BR2_TOOLCHAIN_USES_UCLIBC # gettid
depends on BR2_USE_MMU # libglib2
select BR2_PACKAGE_LIBGLIB2
help
@@ -15,8 +16,10 @@ config BR2_PACKAGE_WIREPLUMBER
https://pipewire.pages.freedesktop.org/wireplumber/
-comment "wireplumber needs a toolchain w/ wchar, threads and Lua >= 5.3"
+comment "wireplumber needs a glibc or musl toolchain w/ wchar, threads and Lua >= 5.3"
depends on BR2_PACKAGE_PIPEWIRE
depends on BR2_USE_MMU
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || \
+ BR2_TOOLCHAIN_USES_UCLIBC || \
(!BR2_PACKAGE_LUA_5_3 && !BR2_PACKAGE_LUA_5_4)
+
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-14 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 16:20 [Buildroot] [PATCH 1/4] package/pipewire: bump version to 1.6.3 Bernd Kuhls
2026-04-14 16:20 ` Bernd Kuhls [this message]
2026-04-14 16:20 ` [Buildroot] [PATCH 3/4] package/wireplumber: bump version to 0.5.14 Bernd Kuhls
2026-04-14 16:20 ` [Buildroot] [PATCH 4/4] package/pipewire-media-session: bump version to 0.4.3 Bernd Kuhls
-- strict thread matches above, loose matches on Subject: below --
2026-05-11 18:17 [Buildroot] [PATCH 1/4] package/pipewire: bump version to 1.6.4 Bernd Kuhls
2026-05-11 18:17 ` [Buildroot] [PATCH 2/4] package/wireplumber: mark broken on uClibc Bernd Kuhls
2026-02-26 22:11 [Buildroot] [PATCH 1/4] package/pipewire: bump version to 1.6.0 Bernd Kuhls
2026-02-26 22:11 ` [Buildroot] [PATCH 2/4] package/wireplumber: mark broken on uClibc Bernd Kuhls
2025-11-30 7:48 [Buildroot] [PATCH 1/4] package/pipewire: bump version to 1.4.9 Bernd Kuhls
2025-11-30 7:48 ` [Buildroot] [PATCH 2/4] package/wireplumber: mark broken on uClibc Bernd Kuhls
2025-11-30 21:40 ` 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=20260414162028.2141018-2-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@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 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.