According to the ncurses 6.0 release notes (the site is at
"https://www.gnu.org/software/ncurses/";), the intent of the release is
to provide a new stable ABI,
which is binary-incompatible with ncurses 5, but it can still be
configured to support the ncurses5. Because this release introduces
s
According to the ncurses 6.0 release notes (the site is at
"https://www.gnu.org/software/ncurses/";), the intent of the release is
to provide a new stable ABI,
which is binary-incompatible with ncurses 5, but it can still be
configured to support the ncurses5. Because this release introduces
sy
On Wed, Jan 20, 2016 at 5:30 PM, Robert Yang wrote:
>
> I had talked with Dengke, we have upgraded ncurses to 6, so remove
> --with-abi-version=5 seems better. He had tested world and sdk
> build based on oe-core. He will test it based on meta-openembedded.
we need to ensure that all apps using n
On 01/20/2016 05:33 PM, Richard Purdie wrote:
On Wed, 2016-01-20 at 04:30 -0500, Dengke Du wrote:
drop the compatible option --with-abi-version=5
This says what the patch does, but not why.
I had talked with Dengke, we have upgraded ncurses to 6, so remove
--with-abi-version=5 seems better
On Wed, 2016-01-20 at 04:30 -0500, Dengke Du wrote:
> drop the compatible option --with-abi-version=5
This says what the patch does, but not why.
Why should we do this? Does any of our software depend on the v5 ABI?
How did you test this?
Cheers,
Richard
--
drop the compatible option --with-abi-version=5
Signed-off-by: Dengke Du
---
meta/recipes-core/ncurses/ncurses.inc| 10 +-
meta/recipes-core/ncurses/ncurses_6.0.bb | 1 -
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/meta/recipes-core/ncurses/ncurses.inc
b/meta/rec
