Closed vimproved closed 2 weeks ago
A workaround for this seems to be setting arch = "linux-musl-x86_64"
in luarocks_config to avoid grabbing linux-x86_64 binaries, but I'm not sure if this has other side effects.
Thanks for reporting.
I think for now the best option is to check the architecture in rocks.nvim and only enable rocks-binaries for the supported architectures.
I'll look into that.
@vimproved what's the output of vim.uv.os_uname()
on your system?
@vimproved what's the output of
vim.uv.os_uname()
on your system?
{
machine = "x86_64",
release = "6.10.2-gentoo",
sysname = "Linux",
version = "#2 SMP PREEMPT_DYNAMIC Mon Jul 29 17:49:13 UTC 2024"
}
Thanks. You'll be able to disable the binary servers when #494 has been merged and released.
On systems using musl, binaries from rocks-binaries will not work by default, and there's no way to force luarocks to compile from source at the current moment (e.g. a config option). As an example, if you set up a barebones rocks.nvim installation on a musl system and then run
:Rocks install tree-sitter-bash
, you will end up with a binary linked against glibc that will therefor fail to load:Or for another example, if you reinstall or update toml-edit through rocks.nvim after bootstrapping, then it will attempt to use the binary linked against glibc and throw this error on startup: