Re: ncurses 6.0 and cur_term function

[Thomas Dickey]

On Sun, Sep 20, 2015 at 06:13:03PM +0200, Ondřej Súkup wrote:
> hello,
> 
> why is in ncurses-6.0:
> 
> $ readelf -a libncurses.so.6 | grep cur_term
> 000000228328  006d00000007 R_X86_64_JUMP_SLO 0000000000000000 _nc_cur_term + 0
>    109: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND
> address@hidden (24)
> 
> $ readelf -a libncurses.so.5 | grep cur_term
>  000000225f70  003900000006 R_X86_64_GLOB_DAT 0000000000000000 cur_term + 0
>     57: 0000000000000000     0 OBJECT  GLOBAL DEFAULT  UND
> address@hidden (29)

Compare with the source code:

> fgrep -n cur_term *.map
ncurses.map:879:                cur_term;
ncursest.map:344:               _nc_cur_term;
ncursest.map:446:               _nc_get_cur_term;
ncursest.map:447:               _nc_get_cur_term_sp;
ncursestw.map:344:              _nc_cur_term;
ncursestw.map:452:              _nc_get_cur_term;
ncursestw.map:453:              _nc_get_cur_term_sp;
ncursesw.map:186:               cur_term;

For instance, you may be using ncurses 6.0 on OpenSUSE, where they've
bent the rules a little to make tinfo the same as for the threaded
(libncursest) library.  There are as usual pros/cons about doing that.

(I didn't make it easy to do this, but I didn't make it impossible...)

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

signature.asc
Description: Digital signature