Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] poco: fix sh4a fenv build failure
Date: Mon, 25 Nov 2013 20:38:01 +0200	[thread overview]
Message-ID: <20131125183801.GR32436@tarshish> (raw)
In-Reply-To: <20131125181121.06f6a801@skate>

Hi Thomas,

On Mon, Nov 25, 2013 at 06:11:21PM +0100, Thomas Petazzoni wrote:
> Dear Baruch Siach,
> 
> On Mon, 25 Nov 2013 18:47:28 +0200, Baruch Siach wrote:
> > Disable FP environment on sh4a. Fixes
> > http://autobuild.buildroot.net/results/8dc9bca5969d455cc30206fc1ae6e1d3ba6eb6ca/.
> > 
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> >  package/poco/poco.mk | 5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/package/poco/poco.mk b/package/poco/poco.mk
> > index a18f209..3516c04 100644
> > --- a/package/poco/poco.mk
> > +++ b/package/poco/poco.mk
> > @@ -34,6 +34,11 @@ ifeq ($(LIBC),uclibc)
> >  POCO_CONF_OPT += --no-fpenvironment --no-wstring
> >  endif
> >  
> > +# sh4a is missing FE_DOWNWARD and FE_UPWARD in its fenv.h
> > +ifeq ($(BR2_sh4a),y)
> > +POCO_CONF_OPT += --no-fpenvironment
> > +endif
> 
> Just curious, is this (the fact that SH4 fenv.h lacks some definitions)
> something specific to uClibc, or something that is also true for
> glibc/eglibc?

This also affects (e)glibc. See 
http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/70784.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2013-11-25 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 16:47 [Buildroot] [PATCH] poco: fix sh4a fenv build failure Baruch Siach
2013-11-25 17:11 ` Thomas Petazzoni
2013-11-25 18:38   ` Baruch Siach [this message]
2013-11-26 11:41 ` Peter Korsgaard

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=20131125183801.GR32436@tarshish \
    --to=baruch@tkos.co.il \
    --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