From: MarleDK <MarleDK@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ncurses: add libtinfo.so
Date: Tue, 28 Apr 2020 11:34:44 +0200 [thread overview]
Message-ID: <20200428093444.keHs4cqCmYSI09Gq-YzfdXe4xE1jDzU-DldeVVTGaBE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21409@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
New comment by MarleDK on void-packages repository
https://github.com/void-linux/void-packages/pull/21409#issuecomment-620493367
Comment:
> Does this resolve the other issues mentioned in #11718 from the last time you tried to enable it @pullmoll?
Oh, I didn't know this had already been tried and that there were any problems.
Is there a way I can test problems with dependencies?
And if this way of adding libtinfo is not possible, would it perhaps be a good idea to simply copy the ncurses template, into a new tinfo-libs package, which would build ncurses with tinfo, but only copy over the libtinfo.so library?
Or simply add a symlink called libtinfo.so to libncurses.so?
The way I understand this to work, is, that when you build ncurses with `--with-termlib` it removes some functions from the libncurses.so and puts them into libtinfo.so (*I verified this by building both with and without `--with-termlib`, and then using `nm -D` to extract exposed symbols, combining the results, and then diff'ing on the ncurses without termlib*).
This way libncurses.so would stay the same, and we would only add libtinfo.so.
next prev parent reply other threads:[~2020-04-28 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 18:59 [PR PATCH] " MarleDK
2020-04-27 19:22 ` [PR PATCH] [Updated] " MarleDK
2020-04-27 22:51 ` Duncaen
2020-04-28 9:34 ` MarleDK [this message]
2020-04-28 11:10 ` pullmoll
2020-04-28 11:16 ` pullmoll
2020-04-28 18:23 ` MarleDK
2020-05-15 21:12 ` pullmoll
2020-05-25 9:03 ` [PR PATCH] [Updated] " MarleDK
2020-05-25 9:06 ` MarleDK
2020-05-26 6:36 ` [PR PATCH] [Updated] " MarleDK
2020-05-27 5:46 ` MarleDK
2020-05-27 5:48 ` MarleDK
2020-05-27 14:29 ` [PR PATCH] [Merged]: " pullmoll
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200428093444.keHs4cqCmYSI09Gq-YzfdXe4xE1jDzU-DldeVVTGaBE@z \
--to=marledk@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).