All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Confused by the <fenv> implementation, causing gsl build issues
Date: Thu, 18 Oct 2012 21:14:51 +0200	[thread overview]
Message-ID: <20121018211451.3d1af865@skate> (raw)
In-Reply-To: <13a751bd21c.19da.2760.rep.dot.nop@gmail.com>


On Thu, 18 Oct 2012 20:21:28 +0200, Bernhard Reutner-Fischer wrote:

> > 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.

Well, at this point I am not interested in any particular target. I am
interested in having uClibc building a correct toolchain, that doesn't
contain headers describing functions that it doesn't implement, causing
build issues in various userspace packages.

So I guess we should simply disable the possibility of enabling fenv
support on those architectures that don't have the necessary code.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-10-18 19:14 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
2012-10-18 19:14       ` 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=20121018211451.3d1af865@skate \
    --to=thomas.petazzoni@free-electrons.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 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.