Is it possible to depend on internal toolchain when uClibc is in use?
Hi Buildroot maintainers and developers,
now that my uClibc-ng patches landed in git master I would like to enable some packages, which were disabled because of missing features inside uClibc-ng default config (fenv, uchar).
When I would add f.e. quickjs it would fail in the autobuilders because of external bootlin toolchains, which does not contain these features, yet.
Is there a way to describe this situation in Kconfig language?
So depends on buildroot internal toolchain if uClibc is used.
Thanks in advance for any help.
best regards
Waldemar
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Coming back to this old mail...
Quoted 11 lines · Waldemar Brodkorb
Hi Buildroot maintainers and developers,
now that my uClibc-ng patches landed in git master I would like to enable some packages, which were disabled because of missing features inside uClibc-ng default config (fenv, uchar).
When I would add f.e. quickjs it would fail in the autobuilders because of external bootlin toolchains, which does not contain these features, yet.
Is there a way to describe this situation in
Kconfiglanguage?
There isn't, unless we add a symbol _HAS_FENV.
What I propose instead, is to assume from now on that external uClibc
toolchains have fenv and uchar. For the bootlin toolchains that is the case now, and we no longer use any other external toolchains in the autobuilders.
It does mean that people who have an old toolchain won't be able to reliably
use it anymore with modern buildroot. But I don't think that's a problem either, in particular because there's also the 2026.08 release as a boundary.
In other words: go ahead and enable packages that need fenv.h for uClibc.
Regards,
Arnout
Quoted 11 lines
So depends on buildroot internal toolchain if uClibc is used.
Thanks in advance for any help.
best regards
Waldemar_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot