From: "dengke.du@windriver.com" <dengke.du@windriver.com>
To: <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] ncurses: 5.9 0 -> 6.0
Date: Fri, 15 Jan 2016 13:18:13 +0800 [thread overview]
Message-ID: <56988115.3020200@windriver.com> (raw)
In-Reply-To: <13d1f0fbaf650975b460b42e72bcdde74e7b97a7.1452826805.git.dengke.du@windriver.com>
Drop it , use the newer patch, because I specifiy the error remote.
Sorry for inconvenience.
On 2016年01月15日 11:07, Dengke Du wrote:
> To be compatible with ncurses 5, add option '--with-abi-version=5' to EXTRA_OECONF
>
> Signed-off-by: Dengke Du <dengke.du@windriver.com>
> ---
> .../recipes-core/ncurses/{ncurses-5.9 => ncurses-6.0}/config.cache | 0
> .../ncurses/{ncurses-5.9 => ncurses-6.0}/tic-hang.patch | 0
> meta/recipes-core/ncurses/ncurses.inc | 1 -
> meta/recipes-core/ncurses/{ncurses_5.9.bb => ncurses_6.0.bb} | 7 +++----
> 4 files changed, 3 insertions(+), 5 deletions(-)
> rename meta/recipes-core/ncurses/{ncurses-5.9 => ncurses-6.0}/config.cache (100%)
> rename meta/recipes-core/ncurses/{ncurses-5.9 => ncurses-6.0}/tic-hang.patch (100%)
> rename meta/recipes-core/ncurses/{ncurses_5.9.bb => ncurses_6.0.bb} (59%)
>
> diff --git a/meta/recipes-core/ncurses/ncurses-5.9/config.cache b/meta/recipes-core/ncurses/ncurses-6.0/config.cache
> similarity index 100%
> rename from meta/recipes-core/ncurses/ncurses-5.9/config.cache
> rename to meta/recipes-core/ncurses/ncurses-6.0/config.cache
> diff --git a/meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch b/meta/recipes-core/ncurses/ncurses-6.0/tic-hang.patch
> similarity index 100%
> rename from meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
> rename to meta/recipes-core/ncurses/ncurses-6.0/tic-hang.patch
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
> index 27815b8..fbe74d5 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -6,7 +6,6 @@ LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cbc
> SECTION = "libs"
> DEPENDS = "ncurses-native"
> DEPENDS_class-native = ""
> -INC_PR = "r15"
>
> BINCONFIG = "${bindir}/ncurses5-config ${bindir}/ncursesw5-config"
>
> diff --git a/meta/recipes-core/ncurses/ncurses_5.9.bb b/meta/recipes-core/ncurses/ncurses_6.0.bb
> similarity index 59%
> rename from meta/recipes-core/ncurses/ncurses_5.9.bb
> rename to meta/recipes-core/ncurses/ncurses_6.0.bb
> index 22c6230..8587287 100644
> --- a/meta/recipes-core/ncurses/ncurses_5.9.bb
> +++ b/meta/recipes-core/ncurses/ncurses_6.0.bb
> @@ -1,12 +1,11 @@
> require ncurses.inc
>
> -REVISION = "20150329"
> -
> -PR = "${INC_PR}.1"
> +REVISION = "20151024"
>
> SRC_URI += "file://tic-hang.patch \
> file://config.cache \
> "
> # commit id corresponds to the above listed REVISION
> -SRCREV = "6286e14dac28811dbfd325b8d4c23f0d4e37eaf0"
> +SRCREV = "c6b034b4d69f8c9092c2a1b5d5bb718282b2a522"
> S = "${WORKDIR}/git"
> +EXTRA_OECONF += "--with-abi-version=5"
next prev parent reply other threads:[~2016-01-15 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 3:07 [PATCH 0/1] ncurses: 5.9 0 -> 6.0 Dengke Du
2016-01-15 3:07 ` [PATCH 1/1] " Dengke Du
2016-01-15 5:18 ` dengke.du [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-15 5:09 [PATCH 0/1] " Dengke Du
2016-01-15 5:09 ` [PATCH 1/1] " Dengke Du
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=56988115.3020200@windriver.com \
--to=dengke.du@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.