From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] findutils: fix sort dir on updatedb
Date: Thu, 26 Jul 2012 12:07:28 -0700 [thread overview]
Message-ID: <50119570.1020704@linux.intel.com> (raw)
In-Reply-To: <1343203659-23756-1-git-send-email-rongqing.li@windriver.com>
On 07/25/2012 01:07 AM, rongqing.li@windriver.com wrote:
> From: Roy.Li <rongqing.li@windriver.com>
>
> [YOCTO #2826]
>
> m4/nullsort.m4 tries to find sort dir, and write it to updatedb,
> but nullsort.m4 is checking the host dir. Once the sort dirs on
> target and host are different, updatedb will fail due to wrong
> sort dir.
>
> Since we always have sort under ${bindir}, so we can assign it
> directly.
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
> meta/recipes-extended/findutils/findutils_4.4.2.bb | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-extended/findutils/findutils_4.4.2.bb b/meta/recipes-extended/findutils/findutils_4.4.2.bb
> index 127eb4b..218bf83 100644
> --- a/meta/recipes-extended/findutils/findutils_4.4.2.bb
> +++ b/meta/recipes-extended/findutils/findutils_4.4.2.bb
> @@ -1,6 +1,6 @@
> require findutils.inc
>
> -PR = "r4"
> +PR = "r5"
>
> SRC_URI += "file://01-27017.patch \
> file://02-28824.patch \
> @@ -15,4 +15,6 @@ SRC_URI[sha256sum] = "434f32d171cbc0a5e72cfc5372c6fc4cb0e681f8dce566a0de5b6fccd7
> # http://savannah.gnu.org/bugs/?27299
> CACHED_CONFIGUREVARS += "${@base_contains('DISTRO_FEATURES', 'libc-posix-clang-wchar', 'gl_cv_func_wcwidth_works=yes', '', d)}"
>
> +EXTRA_OECONF += "ac_cv_path_SORT=${bindir}/sort"
> +
> BBCLASSEXTEND = "native"
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-07-26 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 8:07 [PATCH] findutils: fix sort dir on updatedb rongqing.li
2012-07-26 19:07 ` Saul Wold [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=50119570.1020704@linux.intel.com \
--to=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox