From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] FENV support in uClibc-ng
Date: Sat, 15 Aug 2026 09:39:04 +0200 [thread overview]
Message-ID: <aoAXmAflyCHEGz7V@waldemar-brodkorb.de> (raw)
Dear Buildroot maintainers and developers,
I am planning to submit a new package for chawan, a
nice TUI browser. It has JS support and needs FENV support in
the C library. Can we globally enable FENV support in
uClibc-ng? I measured the size for a default aarch64
build with and without FENV support enabled.
With FENV support enabled:
608992 Aug 15 09:07 libuClibc-1.0.59.so
Without FENV support enabled:
584416 Aug 15 09:24 libuClibc-1.0.59.so
Should we add another option for 24kb?
uClibc-ng also gained support for uchar functions a while back.
tpm2-tools needs it. It adds approx. 5kb to the C library.
What should we do here? Enable uchar automatically, when wchar is enabled?
Or is there another better solution I am not seeing?
I would like to support more packages by default for uClibc-ng users.
What you think?
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-08-15 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 7:39 Waldemar Brodkorb [this message]
2026-08-15 19:45 ` [Buildroot] FENV support in uClibc-ng 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=aoAXmAflyCHEGz7V@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