From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boost: correctly disable icu in locale if needed
Date: Sun, 7 Apr 2019 22:25:19 +0200 [thread overview]
Message-ID: <20190407222519.01e928a6@windsurf> (raw)
In-Reply-To: <20180713174247.4005-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
On Fri, 13 Jul 2018 19:42:47 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> boost doesn't take into account --without-icu flag and links
> libboost_locale with icu if it founds it in staging directory
>
> So use boost.locale.icu to fix this issue
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/boost/boost.mk | 6 ++++++
> 1 file changed, 6 insertions(+)
This patch is still pending in patchwork. Is it still needed ? You send
a number of Boost fixes since then, and the last Boost build errors I
can see at http://autobuild.buildroot.net/?reason=boost% are:
- Download failure due to DNS resolution problem (late March)
- Internal compiler error on Xtensa, mips64, ARC (dating back from
January/February)
Could you check whether your patch would still be needed or not ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-07 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 17:42 [Buildroot] [PATCH 1/1] boost: correctly disable icu in locale if needed Fabrice Fontaine
2018-07-14 20:41 ` Thomas Petazzoni
2018-07-14 21:04 ` Fabrice Fontaine
2018-07-14 21:21 ` Thomas Petazzoni
2019-04-07 20:25 ` Thomas Petazzoni [this message]
2019-04-07 20:39 ` Fabrice Fontaine
2019-04-07 20:45 ` Max Filippov
2019-04-07 21:09 ` Max Filippov
2019-04-08 7:21 ` Thomas Petazzoni
2019-04-08 15:53 ` Max Filippov
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=20190407222519.01e928a6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox