From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Scilab - ghc-bin library link
Date: Tue, 12 Jul 2022 04:15:33 +0200 [thread overview]
Message-ID: <20220712021533.JxN-z8rxsgWNFmJQMnB33B6f0FXVbnn1d7mXEJJ3rR4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24544@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
Closed issue by anjandev on void-packages repository
https://github.com/void-linux/void-packages/issues/24544
Description:
### System
* xuname:
* Void 5.8.5_1 x86_64 GenuineIntel notuptodate rDFFF
* package:
* ghc-bin-8.8.3_1
### Expected behavior
Downloading the binary of scilab opens normally. To obtain the binary, see:
https://www.scilab.org/download/6.1.0
However I get an error like:
```
scilab-cli-bin: error while loading shared libraries: libtinfo.so.5:
```
So I ran `xlocate libtinfo.so.5` and I got
```
ghc-bin-8.8.3_1 /usr/lib/ghc-8.8.3/rts/libtinfo.so.5 ->
/usr/lib/libncursesw.so.6
```
So I assumed installing `ghc-bin-8.8.3_1` would fix my bug but it didnt.
### Actual behavior
Still got the error:
```
scilab-cli-bin: error while loading shared libraries: libtinfo.so.5:
```
after installing ghc-bin-8.8.3_1
### Steps to reproduce the behavior
1. Download the scilab binary and try to `./bin/scilab`
2. Get library error
3. Try to install `ghc-bin-8.8.3_1` to fix
4. Get library error again
prev parent reply other threads:[~2022-07-12 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 8:50 [ISSUE] Scilab anjandev
2020-08-30 8:55 ` Scilab - ghc-bin library link anjandev
2020-08-30 8:56 ` anjandev
2022-03-29 8:15 ` Preferencesoft
2022-06-28 2:15 ` github-actions
2022-07-12 2:15 ` github-actions [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220712021533.JxN-z8rxsgWNFmJQMnB33B6f0FXVbnn1d7mXEJJ3rR4@z \
--to=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).