Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package: add the poco C++ libraries collection
Date: Mon, 26 Sep 2011 22:32:29 +0200	[thread overview]
Message-ID: <87pqinvyci.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110926064459.GB28996@sapphire.tkos.co.il> (Baruch Siach's message of "Mon, 26 Sep 2011 09:44:59 +0300")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 >> The FE_* macros afaik only supposed to be defined if the arch can
 >> efficiently handle it, which isn't the case for ARM.

 Baruch> It builds here for ARM (BR2_ARM_TYPE="ARM926T") using the CodeSourcery 
 Baruch> toolchain (with a little toolchain support fix I'll send shortly).

Indeed. The codesourcery toolchain presumably uses glibc. The problem is
with uClibc - But I don't want to add a package which doesn't work with
the internal toolchain.

 >> fenv.h the
 >> supporting functions are only enabled on uClibc if UCLIBC_HAS_FENV is
 >> enabled in the .config, which it isn't for our uClibc defconfigs.
 >> 
 >> I'm not exactly sure how to fix this. Any ideas?

 Baruch> Is there a way to depend on UCLIBC_HAS_FENV?
 Baruch> Is depending on glibc an option?

I would rather see a patch which uses the dummy fenv implementation on
uClibc without UCLIBC_HAS_FENV.

You can detect that using something like

#include <fetures.h>
#if defined(__UCLIBC__) && !defined (__UCLIBC_HAS_FENV__)
..

But I haven't looked at the poco build system to see how easy that would
be.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-09-26 20:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 12:11 [Buildroot] [PATCHv2] package: add the poco C++ libraries collection Baruch Siach
2011-09-25 21:50 ` Peter Korsgaard
2011-09-26  6:44   ` Baruch Siach
2011-09-26 20:32     ` Peter Korsgaard [this message]
2011-09-27 16:26       ` Baruch Siach
2011-09-27 19:19         ` Peter Korsgaard
2011-10-02  6:41           ` Baruch Siach
2011-10-02 18:59             ` 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=87pqinvyci.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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