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: Tue, 27 Sep 2011 21:19:01 +0200	[thread overview]
Message-ID: <87sjnhvlne.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110927162627.GB5437@sapphire.tkos.co.il> (Baruch Siach's message of "Tue, 27 Sep 2011 19:26:27 +0300")

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

Hi,

 Baruch> Well, it seems that the Poco configure script can do just that
 Baruch> when told to.  The --no-fpenvironment option replaces
 Baruch> FPEnvironment_C99.h with FPEnvironment_DUMMY.h. You can even
 Baruch> pass --no-wstring to disable std::wstring support. So the
 Baruch> question is, is there a way to detect the 'defined(__UCLIBC__)
 Baruch> && !defined (__UCLIBC_HAS_FENV__)' condition at configuration
 Baruch> time? This seems to be much cleaner than patching the code for
 Baruch> build time detection.

Ahh ok, good. As far as I can see, the uClibc fenv support is not really
extensive enough to ever work, so simply detecting uClibc should be
enough. Remember we can use uClibc through
internal/external/crosstool-ng toolchains, so you'll need to do
something like

ifeq ($(BR2_TOOLCHAIN_BUILDROOT)$(BR2_TOOLCHAIN_EXTERNAL_UCLIBC)$(BR2_TOOLCHAIN_CTNG_uClibc),y)
POCO_CONF_OPT += --no-fpenvironment
endif

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-09-27 19:19 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
2011-09-27 16:26       ` Baruch Siach
2011-09-27 19:19         ` Peter Korsgaard [this message]
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=87sjnhvlne.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