From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] package/chawan: new package
Date: Fri, 23 Oct 2026 20:41:38 +0200 [thread overview]
Message-ID: <atupnhi22O6wWwIz@windsurf> (raw)
In-Reply-To: <atszrpfaNpx3zWmi@waldemar-brodkorb.de>
On Fri, Oct 23, 2026 at 12:15:10PM +0200, Waldemar Brodkorb wrote:
> > arm | chawan-0.4.4 | NOK | https://autobuild.buildroot.org/results/35f6ff053723bf0d16ac5b425cf943bac01a4418 |
>
> chawan needs fenv.h, which is only available for a hard-float
> uClibc-ng toolchain. Here arm soft-float is in use. How should I fix this? Any
> suggestion?
So far we have ad-hoc dependencies in each package, so as a initial
fix I would suggest to do the same: exclude architecture/toolchain
combo that don't provide fenv.h.
On this initial fix is done, a better handling of fenv dependencies
would be nice. If you "git grep -i fenv" in Buildroot, you will see
that we have lots of packages that have custom dependencies to
workaround fenv availability issues.
Having in toolchain/Config.in some nice BR2_TOOLCHAIN_HAS_FENV_xyz
options (my understanding is that it cannot be just a single
BR2_TOOLCHAIN_HAS_FENV, because there are multiple exceptions, and
some architecture/toolchains support some which are sufficient for
some packages, but lack others which are needed by other packages).
> > or1k | chawan-0.4.4 | NOK | https://autobuild.buildroot.org/results/2aa8986b4161c9ce25d4bddf8c29d1b204893e0b |
>
> OpenRISC is not supported. How would I express this in Config.in?
> Any suggestion?
As usual:
config BR2_PACKAGE_CHAWAN_ARCH_SUPPORTS
bool
default y
depends on !BR2_or1k
config BR2_PACKAGE_CHAWAN
bool "chawan"
depends on BR2_PACKAGE_CHAWAN_ARCH_SUPPORTS
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-23 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 7:53 [Buildroot] [PATCH v2 2/2] package/chawan: new package Waldemar Brodkorb
2026-10-20 20:39 ` Thomas Petazzoni via buildroot
2026-10-20 22:30 ` Waldemar Brodkorb
2026-10-23 7:35 ` Thomas Petazzoni via buildroot
2026-10-23 10:15 ` Waldemar Brodkorb
2026-10-23 10:27 ` Fiona Klute via buildroot
2026-10-23 18:41 ` Thomas Petazzoni via buildroot [this message]
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=atupnhi22O6wWwIz@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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 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.