From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: fix build on ARC
Date: Fri, 21 Aug 2015 10:43:02 +0200 [thread overview]
Message-ID: <20150821104302.12c70b92@free-electrons.com> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE646578420F@DE02WEMBXB.internal.synopsys.com>
Alexey,
On Thu, 20 Aug 2015 08:26:52 +0000, Alexey Brodkin wrote:
> Even though it's good to have this patch for fixing Boost building I'm not sure
> what this hack causes in runtime. Remember I mentioned these checks for
> GLIBC version are spread all around their sources.
It fixes that particular problem. There may indeed be other problems,
which we can only resolve by having ARC users running Boost based
applications.
> Anyways I see it is already applied so let's live with it for now.
> And I assume once:
> [1] ARC switches from GitHub based uClibc to uClibc-ng in Buildroot
> [2] uClibc-ng bumps to 1.0.6
> we'll get rid of that patch, correct?
Yes, of course, once the _GLIBC_MINOR bump is in a released version of
uClibc-ng, and we have rebuilt the external toolchains, we will drop
this patch from Boost. Do not hesitate to send such a patch series when
time comes.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-21 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 18:26 [Buildroot] [PATCH] boost: fix build on ARC Thomas Petazzoni
2015-08-19 20:57 ` Peter Korsgaard
2015-08-19 21:04 ` Thomas Petazzoni
2015-08-20 8:41 ` Alexey Brodkin
2015-08-20 8:26 ` Alexey Brodkin
2015-08-21 8:43 ` 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=20150821104302.12c70b92@free-electrons.com \
--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