[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?
From: |
Thomas Dickey |
Subject: |
Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1? |
Date: |
Thu, 1 Mar 2018 10:37:21 -0500 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Thu, Mar 01, 2018 at 08:09:17AM +0100, Dr. Werner Fink wrote:
> On Wed, Feb 28, 2018 at 05:48:15PM +0000, Sven Joachim wrote:
> > Am 28.02.2018 um 12:35 schrieb Dr. Werner Fink:
> >
> > > On Tue, Feb 27, 2018 at 09:18:04PM +0000, Thomas Dickey wrote:
> > >> b) link everything against "ncurseswt"
> > >
> > > That means enforce every package to use the libncursew/libtinfow ?
> > > At least all python3 and its modules could be an option
> >
> > Or, alternatively, configure libncursesw with "--with-termlib=tinfo" and
> > install the same tinfo library for the wide and non-wide configurations,
> > getting rid of libtinfow entirely. This is what Fedora and Debian do.
>
> This I had done the last twenty years and run into a problem where last
> year libtinfo and libtinfow become binary distinct resulting in a huge
> number of bugs as every program using libncursesw had crashed
I recall fixing more than one problem of that nature, but don't
recall it being delayed and (since the fixes are easily backported)
don't see it as a reason to not do as Sven suggests.
At the moment I'm working on an improvement to report_offsets to make
it easier to see these incompatibilities...
--
Thomas E. Dickey <address@hidden>
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature