From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-17
Date: Tue, 19 Feb 2019 11:38:34 +0100 [thread overview]
Message-ID: <20190219113834.073a4630@windsurf.home> (raw)
In-Reply-To: <20190218150524.58b7f1a1@x230>
Hello,
On Mon, 18 Feb 2019 15:05:24 +0100
Gwenhael Goavec-Merou <gwenj@trabucayre.com> wrote:
> fftw is unable to find libquadmath.so but this library is missing in
> x86_64-ctng_locales-linux-gnu.tar.xz.
Grmfmfm. We currently have:
config BR2_TOOLCHAIN_HAS_LIBQUADMATH
bool
default y if BR2_i386 || BR2_x86_64
However, it turns out that libquadmath can be disabled in gcc, and
guess what, the gcc in the toolchain causing the failure has been built
with --disable-libquadmath.
So it seems like we need to turn this into a real Config.in option:
- BR2_TOOLCHAIN_HAS_LIBQUADMATH remains a hidden option, has no
default value, and a depends on BR2_i386 || BR2_x86_64
- The internal toolchain backend selects it because we always enable
it for internal toolchains (to be checked)
- All pre-defined external toolchain packages must be updated to
select it
- toolchain-external-custom needs to be extended with a
BR2_TOOLCHAIN_EXTERNAL_LIBQUADMATH option that users can set/unset.
It should depends on BR2_i386 / BR2_x86_64, default to yes, and
select BR2_TOOLCHAIN_HAS_LIBQUADMATH.
- A check needs to be added in toolchain/helpers.mk to verify that the
value of BR2_TOOLCHAIN_HAS_LIBQUADMATH matches the presence/absence
of libquadmath in the toolchain.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-19 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-17 Thomas Petazzoni
2019-02-18 14:05 ` Gwenhael Goavec-Merou
2019-02-19 10:38 ` Thomas Petazzoni [this message]
2019-02-20 12:47 ` Arnout Vandecappelle
2019-02-20 12:51 ` Thomas Petazzoni
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=20190219113834.073a4630@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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