Wasmer 2.1's LLVM depends on libtinfo.so.5

[omarabid]

trafficstars

I've installed wasmer in Archlinux using the terminal command provided in the landing page

curl https://get.wasmer.io -sSfL | sh

However, some libraries seems to be missing. Wasmer doesn't run and throws the following error

./wasmer: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

This can be fixed by installing ncurses5-compat-libs from the community repo

yay -S ncurses5-compat-libs

[jcaesar]

(Interestingly, installing wasmer with pacman -S wasmer on archlinux yields binaries that don't depend on libtinfo… oO)

[SamuraiCrow]

pacman -S wasmer does work on Manjaro as well but doesn't install WAPM. I tried installing the WAPM package from AUR and it failed. The plot thickens.

[Amanieu]

This happened because Wasmer 2.1 switched to using the official LLVM libraries releases. Previously, it used custom LLVM builds which specifically disabled terminfo support in LLVM (which we don't actually need and is causing this issue). For now the workaround of installing ncurses5-compat-libs should be enough but in the future we might want to start using custom LLVM builds again.

[ryanoneill]

FYI, I encountered this on a fairly standard Linux Mint 20.3 (Una) install. Installing libncurses5 via apt resolved the issue. Thanks!

[kenorb]

Same on Ubuntu 21.10.

[jonaprieto]

On a fresh Fedora 36, the proposed solutions don't work. I tried, e.g., sudo dnf install ncurses-compat-libs to fix it without any success. I get:

wasmer: /lib64/libtinfo.so.5: no version information available (required by wasmer)
wasmer 2.3.0

[jcaesar]

@jonaprieto It prints that message, but wasmer still works, right?

[jonaprieto]

Yes. Indeed.

[brainwo]

Got the same issue on Arch Linux, installed via pacman. Running the latest 2.3.0 version.

[syrusakbary]

Wasmer needs to stop depending on libtinfo for next releases. Thanks for the ping everyone

[ptitSeb]

This is fixed on current version. A custom build of llvm is used and wasmer binary have no dependcies with ncurses. I checked with latest 4.2.0:

$ ldd ~/.wasmer/bin/wasmer
        linux-vdso.so.1 (0x00007ffc14fda000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f73ffa4c000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f73ffa47000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f73ff968000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f73ff74e000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f73ff56d000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7404442000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f73ff54b000)

Closing the ticket. Feel free to re-open if it happens again (but it should not).