From: Saul Wold <sgw@linux.intel.com>
To: Bian Naimeng <biannm@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] icu: fix configure error
Date: Mon, 05 Aug 2013 10:39:50 -0700 [thread overview]
Message-ID: <51FFE366.7010603@linux.intel.com> (raw)
In-Reply-To: <51FF72B7.9070706@cn.fujitsu.com>
On 08/05/2013 02:39 AM, Bian Naimeng wrote:
> If we don't create ${STAGING_ICU_DIR_NATIVE} before doing
> do_configure for cross target, the following will be caught.
>
> |configure: error: No such directory ${cross_buildroot} supplied as
> | the argument to --with-cross-build. Use an absolute path.
> |Configure failed. The contents of all config.log files follows to
> | aid debugging
> |ERROR: oe_runconf failed
>
Is this really needed? Which ICU is failing, the target or -native
version? The target version depends on the -native version which should
have created this directory first.
What are the steps to reproduce this?
Sau!
> Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
>
> ---
> meta/recipes-support/icu/icu.inc | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-support/icu/icu.inc b/meta/recipes-support/icu/icu.inc
> index e3944cd..3987e42 100644
> --- a/meta/recipes-support/icu/icu.inc
> +++ b/meta/recipes-support/icu/icu.inc
> @@ -27,6 +27,7 @@ EXTRA_OECONF_class-native = ""
> # http://bugs.icu-project.org/trac/ticket/9790
> do_configure_prepend() {
> [ -f ${S}/acinclude.m4 ] || cp ${S}/aclocal.m4 ${S}/acinclude.m4
> + [ -d ${STAGING_ICU_DIR_NATIVE} ] || mkdir -p ${STAGING_ICU_DIR_NATIVE}
> }
>
> do_install_append_class-native() {
>
next prev parent reply other threads:[~2013-08-05 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 9:39 [PATCH] icu: fix configure error Bian Naimeng
2013-08-05 17:39 ` Saul Wold [this message]
2013-08-06 9:40 ` Bian Naimeng
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=51FFE366.7010603@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=biannm@cn.fujitsu.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.