[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: |
Tue, 27 Feb 2018 04:23:24 -0500 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Tue, Feb 27, 2018 at 08:22:46AM +0100, Dr. Werner Fink wrote:
> On Mon, Feb 26, 2018 at 10:00:44PM +0000, Thomas Dickey wrote:
> > On Mon, Feb 26, 2018 at 12:12:56PM +0100, Dr. Werner Fink wrote:
> > > Hi,
> > >
> > > just to check binary compatibility I see from a diff of the exported
> > > functions for libtinfo and libtinfow
> >
> > offhand, that looks as expected: the "ncursestw" variant should be
> > supplying all of the symbols that are in "ncursest", but the reverse is
> > not true. (That was also true of the data section, so I assume you've
> > been building/delivering the tinfo "w" flavor).
> >
> > The wide-character library adds entrypoints which support the 32-bit
> > numbers, which use a larger (TERMTYPE2) structure than the one
> > supporting 16-bit numbers (TERMTYPE).
> >
> > I named the new functions with a "2" on the end to denote their
> > relationship to TERMTYPE2.
> >
> > When built as "ncursestw", the older functions accept a "TERMTYPE" (no
> > "2") parameter, and the library converts as needed.
> >
> > Bear in mind that there were a few bug-reports last spring and early
> > summer when I completed those changes, but it seems to be working as
> > designed.
> >
> > By the way, to support 32-bit numbers in terminfo, you'll have to
> > build/link the command-line utilities with the wide-character
> > configuration.
>
> OK ... the only problem seems to be that there are programs out there
> which links to both libtinfo.so.6.1 (threadsafe) as well as to
> libtinfow.so.6.1 (wide+threadsafe) and in the case od phython3 modules
> this could lead to a deadlock if the order is wrong, in other word
I recall that there was (perhaps still) a problem with python loading
different versions of ncurses for readline and the curses module.
Ultimately the fix for that was within python.
--
Thomas E. Dickey <address@hidden>
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature
- Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Dr. Werner Fink, 2018/02/26
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Thomas Dickey, 2018/02/26
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Dr. Werner Fink, 2018/02/27
- Re: [bug-ncurses] Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Dr. Werner Fink, 2018/02/27
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?,
Thomas Dickey <=
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Dr. Werner Fink, 2018/02/27
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Thomas Dickey, 2018/02/27
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Dr. Werner Fink, 2018/02/28
- Re: [bug-ncurses] Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Dr. Werner Fink, 2018/02/28
- Re: Some symbols missed in llib-ltinfo and llib-ltinfot for 6.1?, Sven Joachim, 2018/02/28