unable to execute on ubuntu 22 (jammy)

[stephane-martin]

when starting vale-ls manually or through neovim, it crashes:

$ vale-ls
vale-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by vale-ls)
vale-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by vale-ls)

downloaded vale-ls from: https://github.com/errata-ai/vale-ls/releases/download/v0.4.0/vale-ls-x86_64-unknown-linux-gnu.zip

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"

vale itself runs fine.

[ChrisChinchilla]

Same issue reported by @davidnind

ChrisChinchilla/vale-vscode#61 (comment)

does glib need to be this high? I am not overly familiar with go or linux packaging, but maybe it could be downgraded?

[stephane-martin]

In general, for a binary compiled for an old glibc, running it on a system with a new glibc is fine (backward compatible).

I'm not very familiar with rust, but looking at your workflows, you can try something here: https://github.com/errata-ai/vale-ls/blob/main/.github/workflows/release.yml#L32.

ubuntu-latest means ubuntu 24. So you compile against that new glibc. Just replacing the ubuntu-latest Github runner by ubuntu-22.04 may well be enough.

This would still produce a dynamically linked binary though. So systems even older than ubuntu 22 may still be incompatible. As far as i know rust people tend to compile statically their binaries against musl, another lib C implementation, rather than dynamically against glibc. In cargo build, this is the target x86_64-unknown-linux-musl but my knowledge stops here :-)

[ChrisChinchilla]

I'll see what I can figure out, but this isn't my project or code 😅