From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] package/erlang: enable uClibc support
Date: Sun, 18 Oct 2026 11:29:06 +0200 [thread overview]
Message-ID: <atSRYnTOayKlrbjq@waldemar-brodkorb.de> (raw)
uClibc support was disabled in commit:
fb72418160417e9e872f626c356f898bff49cf48.
This problem is solved in 1.0.59. So in internal
Buildroot toolchains and external Bootlin toolchains.
The change can be backported to stable branches.
Tested with aarch64 and external uClibc Bootlin toolchain.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/erlang/Config.in | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/package/erlang/Config.in b/package/erlang/Config.in
index 724f91123b..d3fe0dbec1 100644
--- a/package/erlang/Config.in
+++ b/package/erlang/Config.in
@@ -15,11 +15,11 @@ config BR2_PACKAGE_ERLANG_ARCH_SUPPORTS
# erlang needs host-erlang
depends on BR2_PACKAGE_HOST_ERLANG_ARCH_SUPPORTS
-comment "erlang needs a glibc or musl toolchain w/ dynamic library, threads, wchar"
+comment "erlang needs a toolchain w/ dynamic library, threads, wchar"
depends on BR2_USE_MMU # fork()
depends on BR2_PACKAGE_ERLANG_ARCH_SUPPORTS
depends on BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HAS_THREADS \
- || !BR2_USE_WCHAR || BR2_TOOLCHAIN_USES_UCLIBC
+ || !BR2_USE_WCHAR
config BR2_PACKAGE_ERLANG
bool "erlang"
@@ -27,7 +27,6 @@ config BR2_PACKAGE_ERLANG
depends on BR2_USE_WCHAR
depends on !BR2_STATIC_LIBS
depends on BR2_TOOLCHAIN_HAS_THREADS
- depends on !BR2_TOOLCHAIN_USES_UCLIBC
depends on BR2_PACKAGE_ERLANG_ARCH_SUPPORTS
select BR2_PACKAGE_ZLIB
help
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-10-18 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 9:29 Waldemar Brodkorb [this message]
2026-10-18 10:18 ` [Buildroot] [PATCH] package/erlang: enable uClibc support Thomas Perale via buildroot
2026-10-19 8:46 ` 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=atSRYnTOayKlrbjq@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
/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