All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/1] ICU: upgrade to 50.1
Date: Mon, 17 Dec 2012 10:23:44 +0800	[thread overview]
Message-ID: <50CE8230.6060209@windriver.com> (raw)
In-Reply-To: <20121214205253.GE8699@jama.jama.net>

On 12/15/2012 04:52 AM, Martin Jansa wrote:
> On Fri, Dec 14, 2012 at 06:08:52PM +0800, Qi.Chen@windriver.com wrote:
>> From: Chen Qi<Qi.Chen@windriver.com>
>>
>> Upgrade ICU to 50.1.
>> All unnecessary patches of previous version are dropped.
> Here it fails with:
>
> ERROR: Logfile of failure stored in:
> /OE/jansa-test/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/icu/50.1-r1/temp/log.do_configure.5863
> | configure:3917: checking for gmake
> | configure:3935: found /usr/bin/gmake
> | configure:3947: result: /usr/bin/gmake
> | configure:3983: error: No such directory
> /OE/jansa-test/shr-core/tmp-eglibc/work/x86_64-linux/icu-native/50.1-r1/icu/source
> supplied as the argument to --with-cross-build. Use an absolute path.
>
> Notice native path when building for target (armv5te). Ah and I'm using
> rmwork so maybe it worked for you, because source from native build was
> still available when you started target build.
>
> Cheers,
>

Thank you for testing it :)
This failure should have been fixed in version 2. Are you using version 
1 of this patch?

Thanks,
Chen Qi




  reply	other threads:[~2012-12-17  2:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 10:08 [PATCH V2 0/1] ICU: upgrade to 50.1 Qi.Chen
2012-12-14 10:08 ` [PATCH V2 1/1] " Qi.Chen
2012-12-14 11:02   ` Burton, Ross
2012-12-14 20:52   ` Martin Jansa
2012-12-17  2:23     ` ChenQi [this message]
2012-12-17 19:42       ` Martin Jansa
2012-12-18  2:16         ` ChenQi

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=50CE8230.6060209@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=martin.jansa@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.