Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-17
Date: Wed, 20 Feb 2019 13:51:31 +0100	[thread overview]
Message-ID: <20190220135131.1cd9cc0f@windsurf> (raw)
In-Reply-To: <23ee4267-a989-942d-4101-15d834008801@mind.be>

Hello,

On Wed, 20 Feb 2019 13:47:08 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:

> > 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.  
> 
>  Or we can say that this is an exceptional situation and exclude this toolchain
> in genrandconfig. fftw-quad is the only package that depends on quadmath.

Yes, that's another approach indeed. I don't mind either way. Perhaps
your approach makes sense, I'm not sure there are really a lot of
toolchains that don't have quadmath support.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-02-20 12:51 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
2019-02-20 12:47     ` Arnout Vandecappelle
2019-02-20 12:51       ` Thomas Petazzoni [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=20190220135131.1cd9cc0f@windsurf \
    --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