From: Maxime Devos <maximedevos@telenet.be>
To: "B. Wilson" <elaexuotee@wilsonb.com>, guix-devel@gnu.org
Subject: Re: Do we want versioned symbols in ncurses?
Date: Tue, 12 Apr 2022 10:22:33 +0200 [thread overview]
Message-ID: <9b452deaad9d57a37c14530e0417aa85e558821d.camel@telenet.be> (raw)
In-Reply-To: <3HT81MHBQR6TK.2S4WQS95XXUR5@"@WILSONB.COM>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
B. Wilson schreef op di 12-04-2022 om 12:04 [+0900]:
> Hey Guix,
>
> Is there any particular reason why our current ncurses packages builds without
> versioned symbols? Upstream specifies only default versions (i.e. via @@), no
> forced ones, so IIUC that should make the library drop-in replaceable for
> everything we have so far. Am I missing something?
>
> Building with symbols is easy enough: just configure --with-versioned-syms=yes.
>
> I ran into this after encountering a project that explicitly uses ncurses
> symbol versions. It is simple enough to carry a custom ncurses in my personal
> channel for this, but if possible I thought it would be cool to have it in the
> main one.
>
> Thoughts?
Debian has identifier some potential problems, quoted from
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788610#5>:
> When using this option, quite a lot of internal symbols which are not
> part of the API are no longer exported, see the attached list.
> Fortunately according to codesearch.debian.net, very few packages
> seem
> to use any of those symbols:
>
> - fpc, in fpcsrc/packages/ncurses/src/form.pp, apparently declares
> _nc_Default_Form and _nc_Default_Field. Probably nobody really
> uses those, but I don't really have a clue of Pascal.
>
> - cmake has a lot of hits since it includes a very outdated copy of
> the form library which is apparently unused. The /usr/bin/ccmake
> binary from the cmake-curses-gui package is linked with the system
> form library and does not use any private symbols from it.
>
> - libncursesada and haskell_ncurses declare _nc_has_mouse, but only
> if NCURSES_VERSION_PATCH < 20081122. Prior to that date,
> _nc_has_mouse was actually part of the API so its removal might
> break some old programs. This might be a case where the symbol
> should actually be exported in order not to break the ABI.
We'll have to investigate if this is also a potential problem here.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-12 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 3:04 Do we want versioned symbols in ncurses? B. Wilson
2022-04-12 8:22 ` Maxime Devos [this message]
2022-04-12 8:27 ` Maxime Devos
2022-04-12 10:43 ` B. Wilson, guix-devel
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b452deaad9d57a37c14530e0417aa85e558821d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=elaexuotee@wilsonb.com \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).