From: Saul Wold <sgw@linux.intel.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] icu: update to upstream version 50.1.1
Date: Fri, 04 Jan 2013 11:05:35 -0800 [thread overview]
Message-ID: <50E727FF.2020502@linux.intel.com> (raw)
In-Reply-To: <CAF6bG8f5d8GbkRtT2L8ZS4ZCJ0n6FUByyZAcJ=M5V-oH5HnxXQ@mail.gmail.com>
On 01/03/2013 06:17 PM, Marko Lindqvist wrote:
> On 4 January 2013 00:11, Saul Wold <sgw@linux.intel.com> wrote:
>> On 12/27/2012 06:44 PM, Marko Lindqvist wrote:
>>>
>>> This seems to fix HarfBuzz compile problems.
>>>
>> Just found a problem with this in my testing:
>>
>>> | configure:3983: error: No such directory
>>> /home/sgw/yocto/builds/world/tmp/sysroots/x86_64-linux/usr/share/icu/50.1.1
>>> supplied as the argument to --with-cross-build. Use an absolute path.
>>
>> Seems that icu lays down a /usr/share/icu/50.1 directory, not a ${PV}, so
>> this needs a little work.
>
> Can you tell anything more about the situation where this came up? I
> tried to reproduce, but icu-native build created, and icu build used
> .../icu/50.1.1/... just right.
>
> Was that with already populated tree where just the icu update patch
> had been applied? I'm guessing if icu-native and icu builds somehow
> happened concurrently, and icu-native was not ready by the time icu
> needed it. Then that 50.1 directory you saw could be leftover from
> earlier version.
>
>
Hmm, when you build the new version of icu-native, what does it create
for you in your tmp/sysroot/x86*-linux/usr/share?
Thanks
Sau!
> - ML
>
next prev parent reply other threads:[~2013-01-04 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 2:44 ICU update Marko Lindqvist
2012-12-28 2:44 ` [PATCH] icu: update to upstream version 50.1.1 Marko Lindqvist
2013-01-03 22:11 ` Saul Wold
2013-01-04 2:17 ` Marko Lindqvist
2013-01-04 19:05 ` Saul Wold [this message]
2013-01-04 19:34 ` Marko Lindqvist
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=50E727FF.2020502@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cazfi74@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.