- Saved searches
- Use saved searches to filter your results more quickly
- libtinfo.so.5: cannot open shared object file #104
- libtinfo.so.5: cannot open shared object file #104
- Comments
- Пакет: libtinfo5 (6.2-0ubuntu2.1 и другие) [security] [universe]
- Original Maintainers (usually from Debian):
- Внешние ресурсы:
- Подобные пакеты:
- shared low-level terminfo library (legacy version)
- Другие пакеты, относящиеся к libtinfo5
- Загрузка libtinfo5
- How To Install libtinfo5 on Ubuntu 20.04
- What is libtinfo5
- Install libtinfo5 Using apt-get
- Install libtinfo5 Using apt
- Install libtinfo5 Using aptitude
- How To Uninstall libtinfo5 on Ubuntu 20.04
- Uninstall libtinfo5 And Its Dependencies
- Remove libtinfo5 Configurations and Data
- Remove libtinfo5 configuration, data, and all of its dependencies
- References
- Summary
- Libtinfo so 5 linux
- Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
- Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
- Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
- Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
- Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
- Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libtinfo.so.5: cannot open shared object file #104
libtinfo.so.5: cannot open shared object file #104
Comments
After the latest software update on my Pop!_OS (which is basically Ubuntu ), spago started to throw an error:
spago: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
After some investigation I found out that I have libtinfo.so.6 not libtinfo.so.5 and the way to fix this problem is to create this symlink:
sudo ln -s /path/to/libtinfo.so.6 /path/to/libtinfo.so.5
I understand that it’s not exactly a spago issue, but I still want to bring this up
- to save people that are facing this issue some googling time
- to find out if this fix is a correct way solve this problem
The text was updated successfully, but these errors were encountered:
After reading that issue I’m not sure there’s a «proper way to fix it» on our side 🤔
Of course an option would be to compile a static binary for Linux.
I wouldn’t want to impose that cost on everyone anyway. If someone really cares, they can patch the binary themselves e.g. https://github.com/justinwoo/easy-purescript-nix/blob/master/spago.nix
But many programs won’t work without ncurses and other dependencies anyway
Turns out the reason why this happens is that we build spago on the fpco/stack-build Docker image, which is based on Ubuntu 16.04, which ships libtinfo.so.5 , while it looks like the latest Ubuntu ships with libtinfo.so.6 .
Since the latest Ubuntu has issues in compiling Haskell (source: a colleague has to use Nix to compile our Haskell stuff on his latest Ubuntu, and this is probably also the reason why FP Complete is still on Ubuntu 16), we probably cannot do anything about this. (short of statically compiling, which I’d avoid for now, as it’s some effort to configure)
So I’ll close this as «we cannot do much», but it’s probably worth adding an entry to the FAQ?
Пакет: libtinfo5 (6.2-0ubuntu2.1 и другие) [security] [universe]
Please consider filing a bug or asking a question via Launchpad before contacting the maintainer directly.
Original Maintainers (usually from Debian):
It should generally not be necessary for users to contact the original maintainer.
Внешние ресурсы:
Подобные пакеты:
shared low-level terminfo library (legacy version)
Другие пакеты, относящиеся к libtinfo5
- зависимости
- рекомендации
- предложения
- enhances
- dep: libc6 (>= 2.16) [не arm64, ppc64el, riscv64] GNU C Library: Shared libraries
также виртуальный пакет, предоставляемый libc6-udeb dep: libc6 (>= 2.17) [arm64, ppc64el] dep: libc6 (>= 2.27) [riscv64]
Загрузка libtinfo5
Архитектура | Версия | Размер пакета | В установленном виде | Файлы |
---|---|---|---|---|
amd64 | 6.2-0ubuntu2.1 | 81,4 Кб | 522,0 Кб | [список файлов] |
arm64 | 6.2-0ubuntu2 | 75,6 Кб | 522,0 Кб | [список файлов] |
armhf | 6.2-0ubuntu2 | 68,6 Кб | 432,0 Кб | [список файлов] |
i386 | 6.2-0ubuntu2.1 | 82,0 Кб | 500,0 Кб | [список файлов] |
ppc64el | 6.2-0ubuntu2 | 94,8 Кб | 666,0 Кб | [список файлов] |
riscv64 | 6.2-0ubuntu2 | 73,3 Кб | 482,0 Кб | [список файлов] |
s390x | 6.2-0ubuntu2 | 78,6 Кб | 530,0 Кб | [список файлов] |
This page is also available in the following languages:
Авторские права © 2023 Canonical Ltd.; См. условия лицензии. Ubuntu это торговый знак компании Canonical Ltd. Об этом сайте.
How To Install libtinfo5 on Ubuntu 20.04
In this tutorial we learn how to install libtinfo5 on Ubuntu 20.04.
What is libtinfo5
The ncurses library routines are a terminal-independent method of updating character screens with reasonable optimization.
This package contains the legacy version of the shared low-level terminfo library. Description-md5: e4089e57710bd30671fca7351b19ae90
There are three ways to install libtinfo5 on Ubuntu 20.04. We can use apt-get , apt and aptitude . In the following sections we will describe each method. You can choose one of them.
Install libtinfo5 Using apt-get
Update apt database with apt-get using the following command.
After updating apt database, We can install libtinfo5 using apt-get by running the following command:
sudo apt-get -y install libtinfo5
Install libtinfo5 Using apt
Update apt database with apt using the following command.
After updating apt database, We can install libtinfo5 using apt by running the following command:
sudo apt -y install libtinfo5
Install libtinfo5 Using aptitude
If you want to follow this method, you might need to install aptitude first since aptitude is usually not installed by default on Ubuntu. Update apt database with aptitude using the following command.
After updating apt database, We can install libtinfo5 using aptitude by running the following command:
sudo aptitude -y install libtinfo5
How To Uninstall libtinfo5 on Ubuntu 20.04
To uninstall only the libtinfo5 package we can use the following command:
sudo apt-get remove libtinfo5
Uninstall libtinfo5 And Its Dependencies
To uninstall libtinfo5 and its dependencies that are no longer needed by Ubuntu 20.04, we can use the command below:
sudo apt-get -y autoremove libtinfo5
Remove libtinfo5 Configurations and Data
To remove libtinfo5 configuration and data from Ubuntu 20.04 we can use the following command:
sudo apt-get -y purge libtinfo5
Remove libtinfo5 configuration, data, and all of its dependencies
We can use the following command to remove libtinfo5 configurations, data and all of its dependencies, we can use the following command:
sudo apt-get -y autoremove --purge libtinfo5
References
Summary
In this tutorial we learn how to install libtinfo5 package on Ubuntu 20.04 using different package management tools: apt, apt-get and aptitude.
Libtinfo so 5 linux
Post by Landeel » Apr 07, 2020 21:17
D.J.Peters wrote: Often you need only a symbolic link that points to libtinfo.so (in case the libtinfo.so.6 is in /usr/lib/)
sudo ln -s /usr/lib/libtinfo.so.5 /usr/lib/libtinfo.so.6
./yagac-linux-x86_64: /lib/x86_64-linux-gnu/libtinfo.so.5: version `NCURSES_TINFO_5.0.19991023′ not found (required by ./yagac-linux-x86_64)
I could install fbc on 20.04, and got it to compile both 32-bit and 64-bit, by installing all those libs:
sudo apt-get install gcc-multilib libncurses-dev libncurses-dev:i386 libx11-dev libx11-dev:i386 libxext-dev libxext-dev:i386 libxpm-dev libxpm-dev:i386 libxrandr-dev libxrandr-dev:i386 libxrender-dev libxrender-dev:i386 libzip-dev libzip-dev:i386 libgl-dev libgl-dev:i386
But then, the resulting executables will require libtinfo.so.6 instead of libtinfo.so.5.
So they won’t work on previous Ubuntu versions. :~(
I love Linux, but what a mess.
badidea Posts: 2551 Joined: May 24, 2007 22:10 Location: The Netherlands
Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Post by badidea » Apr 07, 2020 22:08
Landeel Posts: 777 Joined: Jan 25, 2007 10:32 Location: Brazil Contact:
Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Post by Landeel » Apr 08, 2020 0:05
badidea wrote: Thinking out loud here. What if you ship ‘libtinfo.so.5’ with the game, would that work?
Yes, I think I’ll need to do that. It means I’ll have to ship it with a runner script to set the libpath and load.
Also if I’m going to stick to 20.04, I need to figure out how to compile using the older libs. The glibc that ships with 20.04 is not backwards compatible it seems.
I remember having to do that years ago. I think I have just dropped the ‘.a’ libs in /usr/local/lib/freebasic/. not sure. I’ll test it.
marcov Posts: 3431 Joined: Jun 16, 2005 9:45 Location: Netherlands Contact:
Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Post by marcov » Apr 08, 2020 9:45
I used to try to do this in the past too. Now I only make multiple builds in VMs for the various LTSes, and don’t even attempt to support all distros. Much less work, and the experience is better.
Landeel Posts: 777 Joined: Jan 25, 2007 10:32 Location: Brazil Contact:
Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Post by Landeel » Apr 08, 2020 11:27
Couldn’t get it to compile with a different glibc.
I miss the old standalone fbc.
When I compile from 18.04, the executables are compatible down tô 14.04 if I’m not mistaken.
It’s been a while since such breakage hapenned.
A VM is a solution. I will only need it for the final buils anyway.
Maybe I can setup a minimal container or a chroot.
Hm. a fbc snap with older libs could work.
Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Post by caseih » Apr 08, 2020 19:57
I just built FBC 1.07 on my Centos 8 machine. I had to install the ncurses compatibility libraries to get my old bootstrap version of fbc to run. After building, the fbc compiler, runtime, and subsequent compiled executables all link against libtinfo.so.6, as I would expect. FBC is using the system GCC 8.3.1 compiler.
Note that while the CentOS 8 ncurses-compat-libs rpm supplies libtinfo.so.5 to make existing programs work, it does not provide header files, so the older fbc binaries will not be able to make working executables (no matter what the emitter is) since the new binaries will want to link against libtinfo.so.6 and the FB runtime will want libtinfo.so.5. Bootstrapping the latest fbc from an older version of fbc isn’t too difficult.
On Ubuntu 20.04, either look for a compatibility library, or copy libtinfo.so.5 from another machine and use it just long enough to bootstrap a working version of the latest FBC that targets your system library versions.
I’m not quite sure what you meant when you miss the old standalone FBC. The problem with libtinfo.so.5 has nothing to do with FBC and everything to do with changes in the OS. You’d still encounter this problem even with the 32-bit assembly emitter version of FBC.
Note that all new distros are shipping libtinfo.so.6 now, and not all ship compatibility for libtinfo.so.5. So any binaries you ship will have to take that into account.
Landeel Posts: 777 Joined: Jan 25, 2007 10:32 Location: Brazil Contact:
Re: (L)Ubuntu Focal Fossa (20.04) and libtinfo.so.5
Post by Landeel » Apr 08, 2020 21:11
caseih wrote: I just built FBC 1.07 on my Centos 8 machine. I had to install the ncurses compatibility libraries to get my old bootstrap version of fbc to run. After building, the fbc compiler, runtime, and subsequent compiled executables all link against libtinfo.so.6, as I would expect. FBC is using the system GCC 8.3.1 compiler.
Note that while the CentOS 8 ncurses-compat-libs rpm supplies libtinfo.so.5 to make existing programs work, it does not provide header files, so the older fbc binaries will not be able to make working executables (no matter what the emitter is) since the new binaries will want to link against libtinfo.so.6 and the FB runtime will want libtinfo.so.5. Bootstrapping the latest fbc from an older version of fbc isn’t too difficult.
On Ubuntu 20.04, either look for a compatibility library, or copy libtinfo.so.5 from another machine and use it just long enough to bootstrap a working version of the latest FBC that targets your system library versions.
I’m not quite sure what you meant when you miss the old standalone FBC. The problem with libtinfo.so.5 has nothing to do with FBC and everything to do with changes in the OS. You’d still encounter this problem even with the 32-bit assembly emitter version of FBC.
Note that all new distros are shipping libtinfo.so.6 now, and not all ship compatibility for libtinfo.so.5. So any binaries you ship will have to take that into account.
The thing I miss about the standalone fbc is that it helped me avoid the GLIBC compatibility issue. I used to drop older .a libs (mostly libc.a) in /usr/local/lib/freebasic/. and could get it to compile executables compatible with older distros. I couldn’t make this work with current fbc, but it’s been a while so I really can’t remember the details.
The libtinfo is a different thing. I think I can statically link libtinfo into my executables by dropping the libtinfo.a into /usr/local/lib/freebasic/. , but I’m not sure that’s allowed.
I’m trying to build a FreeBASIC snap with a 18.04 (core18) environment. No luck so far.