unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "B. Wilson" <elaexuotee@wilsonb.com>, guix-devel@gnu.org
To: Maxime Devos <maximedevos@telenet.be>
Subject: Re: Do we want versioned symbols in ncurses?
Date: Tue, 12 Apr 2022 19:43:26 +0900	[thread overview]
Message-ID: <389C64HIRK04D.2QNCN9N8Z1KC1@"@WILSONB.COM> (raw)
In-Reply-To: <96f3b62b9c9e48ff29f597ca4159505be4929f98.camel@telenet.be>

Thanks for the quick turnaround.

> Debian has identifier some potential problems, quoted from
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788610#5>:

Ah, yes. The version script also sets a bunch of symbols to local scope. Good
catch.

Off the top of my head, the only sanity-check I can come up with is a brute
force one: iterate through all referrers of ncurses, and check all their ELFs
for missing symbols.

> FWIW, there will only ever by one ‘version’ of a symbol, according to
> upstream:
> 
> <https://lists.nongnu.org/archive/html/bug-ncurses/2016-01/msg00018.html>
> (also: <https://bugzilla.redhat.com/show_bug.cgi?id=1875587>)
> 
> so I don't quite see the point.

Agreed. I'm not sure it's worth the effort given the above.

For in-tree packages, there is vanishing benefit, but my particular pain
point was using a particular external pre-built .so. Oh well.


      reply	other threads:[~2022-04-13 11:04 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
2022-04-12  8:27 ` Maxime Devos
2022-04-12 10:43   ` B. Wilson, guix-devel [this message]

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='389C64HIRK04D.2QNCN9N8Z1KC1@"@WILSONB.COM' \
    --to=elaexuotee@wilsonb.com \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).