From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libgc: fix build under uClibc
Date: Wed, 23 Apr 2014 15:34:02 +0200 [thread overview]
Message-ID: <20140423153402.6fb6b860@skate> (raw)
In-Reply-To: <0f149850960676b78e6e35678ab580c1e1aba73c.1398254403.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Wed, 23 Apr 2014 15:00:03 +0300, Baruch Siach wrote:
> fenv.h is used in a workaround for a glibc specific bug. However, uClibc lies
> by defining __GLIBC__, but does not provide fenv.h in our default uClibc
> configurations.
>
> Fixes:
> http://autobuild.buildroot.net/results/b2a/b2a1b1e374764855e701ea62fe9f1385ba77ac0d/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> ...01-Fix-build-on-Linux-x86_64-under-uClibc.patch | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 package/libgc/libgc-01-Fix-build-on-Linux-x86_64-under-uClibc.patch
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-23 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 12:00 [Buildroot] [PATCH] libgc: fix build under uClibc Baruch Siach
2014-04-23 13:34 ` 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=20140423153402.6fb6b860@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox