From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure.
Date: Wed, 07 Dec 2011 18:23:57 +0000 [thread overview]
Message-ID: <1323282237.30601.52.camel@ted> (raw)
In-Reply-To: <4EDF991D.1010601@balister.org>
On Wed, 2011-12-07 at 11:49 -0500, Philip Balister wrote:
> On 12/07/2011 11:40 AM, Richard Purdie wrote:
> > On Wed, 2011-12-07 at 10:59 -0500, Philip Balister wrote:
> >> Part of boost needs libraries from icu. Without this, either the build or
> >> image construction fails. (I forget exactly which)
> >
> > That is a fairly heavy dependency to add and we're not seeing builds or
> > images fail due to this being missing as far as I can tell. Do you have
> > any further information on this?
>
> Googling gets me this page:
>
> http://www.boost.org/doc/libs/1_41_0/libs/regex/doc/html/boost_regex/ref/non_std_strings/icu/intro.html
>
> I'm no expert at this unicode stuff, maybe we need to nuild boost
> without unicode?
That sounds preferable since I can't see how we can be using it at
present anyway. I'm hoping we can just disable that bit of boost until
somebody needs it...
Cheers,
Richard
prev parent reply other threads:[~2011-12-07 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:59 [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure Philip Balister
2011-12-07 15:59 ` [PATCH 2/2] qt4.inc : Add uic, moc, rcc, and lrelease to tools package Philip Balister
2011-12-07 16:23 ` Koen Kooi
2011-12-07 16:44 ` Philip Balister
2011-12-07 17:31 ` Paul Eggleton
2011-12-07 16:40 ` [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure Richard Purdie
2011-12-07 16:49 ` Philip Balister
2011-12-07 18:23 ` Richard Purdie [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=1323282237.30601.52.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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