From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 119 - libtinfo.so.5 missing?
Date: Mon, 26 Mar 2018 19:02:11 +0100 [thread overview]
Message-ID: <1522087331.556038.34.camel@ipfire.org> (raw)
In-Reply-To: <01b701d3c3b1$940660b0$bc132210$@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Hello,
where did you install the add-ons from?
-Michael
On Sat, 2018-03-24 at 22:49 +0200, Horace Michael wrote:
> Hi everybody,
>
> When libtinfo.so.5.9 got erased? (lfs/ncurses contains
> rm -vf $(PREFIX)/lib/libtinfo.*)
>
> Nano, htop (and perhaps other apps) need it:
> # htop
> htop: error while loading shared libraries: libtinfo.so.5: cannot open
> shared object file: No such file or directory
>
> nano
> nano: error while loading shared libraries: libtinfo.so.5: cannot open
> shared object file: No such file or directory
>
> I am running a fresh install of core 119
> 3.14.79-ipfire #1 SMP Sun Feb 25 19:02:14 GMT 2018 x86_64 AMD GX-412TC SOC
> AuthenticAMD GNU/Linux
>
> Thank you,
> Horace
>
next prev parent reply other threads:[~2018-03-26 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 20:49 Horace Michael
2018-03-26 18:02 ` Michael Tremer [this message]
2018-03-26 18:09 ` Horace Michael
2018-03-26 18:11 ` Michael Tremer
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=1522087331.556038.34.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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