From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] poco: disable fpenvironment for MIPS without FPU
Date: Tue, 9 Oct 2018 15:05:38 +0200 [thread overview]
Message-ID: <20181009150538.09658891@windsurf> (raw)
In-Reply-To: <20181009122326.12174-1-yegorslists@googlemail.com>
Hello,
On Tue, 9 Oct 2018 14:23:26 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> glibc fixed a bug, that defined FPU capabilities not
This is a bit vague. Which bug? Which commit? Do you have some more
details ?
> available for MIPS without FPU. So add --no-fpenvironment
> to the configuration options for this case.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> package/poco/poco.mk | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/package/poco/poco.mk b/package/poco/poco.mk
> index 018344d5c7..1f3eabd009 100644
> --- a/package/poco/poco.mk
> +++ b/package/poco/poco.mk
> @@ -42,6 +42,13 @@ ifeq ($(BR2_sh4a)$(BR2_nios2),y)
> POCO_CONF_OPTS += --no-fpenvironment
> endif
>
> +# MIPS without FPU
> +ifeq ($(BR2_mips)$(BR2_mipsel)$(BR2_mips64)$(BR2_mips64el),y)
> +ifeq ($(BR2_MIPS_SOFT_FLOAT),y)
Perhaps:
ifeq ($(BR2_mips)$(BR2_mipsel)$(BR2_mips64)$(BR2_mips64el):$(BR2_MIPS_SOFT_FLOAT),y:y)
I'm wondering if we shouldn't introduce some global BR2_ARCH_IS_MIPS
option, or something like that, because we have a lot of places where
we repeat those mips/mipsel/mips64/mips64el conditions. But that is of
course a completely separate discussion.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-09 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 12:23 [Buildroot] [PATCH] poco: disable fpenvironment for MIPS without FPU yegorslists at googlemail.com
2018-10-09 13:05 ` 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=20181009150538.09658891@windsurf \
--to=thomas.petazzoni@bootlin.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.