From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-core@openembedded.org
Subject: Re: [PATCH] boost : Do not use icu when building boost.
Date: Tue, 13 Dec 2011 12:31:47 +0000 [thread overview]
Message-ID: <1323779507.2731.67.camel@ted> (raw)
In-Reply-To: <1323727116-10292-1-git-send-email-philip@balister.org>
On Mon, 2011-12-12 at 16:58 -0500, Philip Balister wrote:
> Without this, boost needs to build icu to create images using
> boost regex. RP inidicated he would rather disable icu, than add an
> extra dependency to the recipe.
>
> Signed-off-by: Philip Balister <philip@balister.org>
> ---
> meta/recipes-support/boost/boost.inc | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-12-13 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 21:58 [PATCH] boost : Do not use icu when building boost Philip Balister
2011-12-13 12:31 ` 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=1323779507.2731.67.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@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