From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Confused by the <fenv> implementation, causing gsl build issues
Date: Thu, 18 Oct 2012 20:21:28 +0200 [thread overview]
Message-ID: <13a751bd21c.19da.2760.rep.dot.nop@gmail.com> (raw)
In-Reply-To: <20121018154240.25b7a7e3@skate>
On 18 October 2012 15:42:40 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>
> On Mon, 15 Oct 2012 00:10:19 +0200, Bernhard Reutner-Fischer wrote:
>
> > > uClibc provides a UCLIBC_HAS_FENV option that can be enabled on any
> > > architecture.
> >
> > Fenv is IIRC only implemented for i386.
>
> Ok, but then why it can be selected on other architectures, and why
> does it install <fenv.h> even on architectures where it is not
> supported?
Please provide patches to add minimal fenv support for the target(s)
you are interested in.
TIA,
Sent with AquaMail for Android
http://www.aqua-mail.com
next prev parent reply other threads:[~2012-10-18 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 10:04 [Buildroot] Confused by the <fenv> implementation, causing gsl build issues Thomas Petazzoni
2012-10-14 22:10 ` Bernhard Reutner-Fischer
2012-10-18 13:42 ` Thomas Petazzoni
2012-10-18 18:21 ` Bernhard Reutner-Fischer [this message]
2012-10-18 19:14 ` 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=13a751bd21c.19da.2760.rep.dot.nop@gmail.com \
--to=rep.dot.nop@gmail.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