"Bootstrap Error" rust-analyzer requires glibc >= 2.28 in latest build. #11558

jhgg · 2022-02-26T03:00:40Z

rust-analyzer no longer will run on Ubuntu 18.04( which bundles glibc 2.27), and other distros which have a glibc older than 2.27.

this issue manifests as a "Bootstrap Error" notably, the extension output will log something along the lines of:

ERROR [2/28/2022, 8:46:56 AM]: Bootstrap error [Error: Failed to execute /home/newuser/.vscode/extensions/matklad.rust-analyzer-0.2.956/server/rust-analyzer --version

when running the binary, we get the following error:

/home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer)
/home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer)

current workarounds are mentioned in this comment: #11558 (comment)

The text was updated successfully, but these errors were encountered:

jhgg · 2022-02-26T03:09:32Z

Compiling from source works, wonder if something changed on the GH actions runner that made it require a newer glibc. 🤔

bjorn3 · 2022-02-26T06:41:53Z

You can use the rust-analyzer from rustup if you need to run it on a system with an older glibc version. The change breaking 18.04 support was probably #10672 which updated the builder from ubuntu 18.04 to 20.04.

lnicola · 2022-02-26T06:45:04Z

It was actually working on 20.04 at the time (I checked and marked it as "potentially breaking" in the changelog, as opposed to "breaking"). Maybe we (or the compiler, in 1.59) recently started using some symbol from 2.28 or 2.29.

jhgg · 2022-02-27T01:33:53Z

This is somewhat problematic for us, because our remote development environment for our company is ubuntu 18.04 at current, which means the rust-analyzer extension will suddenly break in a weird way (the error message isn't that clear about lacking glibc, I had to actually go and execute the bundled r-a binary directly.)

I wonder how many people will run into this issue when this change hits the main release.

To ensure maximum compatibility with the rust-analyzer binary distributed in the vscode extension, should we instead bundle the musl binary?

bjorn3 · 2022-02-27T06:19:37Z

Musl's memory allocator is slower. It may also affect memory usage (positive or negative).

bjorn3 · 2022-02-27T06:20:33Z

In addition using musl would make it impossible to load proc macros compiled for glibc. (which is the default)

jhgg · 2022-02-27T08:27:47Z

Hmm, is there any viable path forward to restore 18.04 support? Ubuntu 18.04 is supported until April 2023, which means it will be in wide use until then (and probably for a while after...)

bjorn3 · 2022-02-27T08:34:52Z

Using the rust-analyzer-preview component from rustup is the easiest way. This one is built to support the exact same glibc versions as rustc.

jhgg · 2022-02-27T08:44:39Z

Is that one regularly updated with each week's r-a release? From a user-friendliness perspective, the vscode extension "just updates" and keeps up to date with the latest version, having to pull from rustup means no more auto updates :/

bjorn3 · 2022-02-27T09:03:10Z

Yes, it get updated every week: https://github.com/rust-lang/rust/pulls?q=is%3Apr+%3Aup%3A+rust-analyzer+is%3Amerged+-label%3Arollup I agree that it is less user friendly.

jhgg · 2022-02-27T09:36:13Z

Would it be possible to just replicate what rustc is doing to compile rust-analyzer here? That way we can maintain same support as the rustup component?

bjorn3 · 2022-02-27T09:49:10Z

Rustc uses a docker image with an older linux distro to build everything. I believe @matklad is worried that it will harm maintenance to do so for rust-analyzer too due to complicating the CI. Currently the exact same steps are used for all platforms for which binaries are released. Using docker on linux would require duplicating this.

lnicola · 2022-02-27T09:57:48Z

We could try to roll back our CI to 18.04, but in general we don't have the same infrastructure as rust-lang/rust and we can't offer the same variety of builds. That's why it's available in rustup.

taikulawo · 2022-02-28T07:45:50Z

We could try to roll back our CI to 18.04, but in general we don't have the same infrastructure as rust-lang/rust and we can't offer the same variety of builds. That's why it's available in rustup.

How I can use RA from rustup? what should I do

taikulawo · 2022-02-28T07:48:22Z

Bootstrap error [Error: Failed to execute /root/.vscode-server/extensions/matklad.rust-analyzer-0.2.956/server/rust-analyzer --version

$ /root/.vscode-server/extensions/matklad.rust-analyzer-0.2.956/server/rust-analyzer --version
> /root/.vscode-server/extensions/matklad.rust-analyzer-0.2.956/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /root/.vscode-server/extensions/matklad.rust-analyzer-0.2.956/server/rust-analyzer)

Distributor ID: Debian
Description: Debian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch

lnicola · 2022-02-28T07:50:03Z

$ rustup toolchain install nightly --component rust-analyzer-preview

Then set rust-analyzer.server.path to ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rust-analyzer.

Matthias247 · 2022-02-28T21:22:12Z

Musl's memory allocator is slower. It may also affect memory usage (positive or negative).

This could be somewhat mitigated by using a custom allocator - e.g. either setting jemalloc or mimalloc via LD_LIBRARY_PATH or as a global allocator in Rust.

I definitely recommend to publish by default an extension which works with older glib versions - because far more distributions than just Ubuntu 18 haven't caught up and will run into issues. Whether that's best achieved using an older Ubuntu builder again or by moving to musl and bundling more dependencies is up to the team :)

rimutaka · 2022-02-28T23:19:07Z

Summary of a workaround

the last working build: 0.2.948
the first broken build: 0.2.956
who is affected: anyone running Ubuntu < v.20

Option 1 - downgrade

1.Open the extension page in VS Code
2. Click on [V] next to Uninstall button
3. Select 0.2.948 and reload

Notes

You will be perpetually stuck on that version.

Option 2 - use pre-prelease via rustup

Install rust-analyzer-preview by running rustup toolchain install nightly --component rust-analyzer-preview
Go to VSCode settings and search for rust-analyzer.server.path. You should see something along these lines
Click on Edit in settings.json and add "rust-analyzer.server.path": "~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rust-analyzer"
Reload VSCode

Notes

You will have to update the extension manually with rustup update

Even if rust-analyzer is built using nightly you can still use stable as your default channel
Component availability: https://rust-lang.github.io/rustup-components-history/

dpypin · 2022-03-01T01:30:06Z

Workaround Option 1 is not working for me. When I try to downgrade to 0.2.948 I get the following error in VSCode:

"Can't install 'matklad.rust-analyzer' extension because it is not compatible with the current version of Visual Studio Code (version 1.64.2)."

sunjay · 2022-03-01T02:49:12Z

Getting the same error as @dpypin for Option 1. When I try Option 2, I don't actually see any rust-analyzer.server.path option. If I put it in manually in settings.json, vscode just says that it is unused. Does that setting work for when the extension is installed remotely over SSH? I followed the rustup step on my remote server, so everything should be installed correctly.

Edit: Worth noting that I have the latest version of vscode which is 1.64.2. I'm currently in the process of downgrading to see if I can get it working again.

sejr · 2022-03-01T05:08:55Z

Is there any way to get one of the previous builds to work with VS Code 1.64.2? This has kinda derailed me in an environment where I can’t use rustup.

lnicola · 2022-03-01T05:22:11Z

@sejr you can download one from https://github.com/rust-analyzer/rust-analyzer/releases, chmod +x it, then set rust-analyzer.server.path.

opensas · 2022-03-05T14:05:37Z

Next monday.

so next monday (2022-03-14) with just reintalling the extension everything should work out of the box on 18.04. right?

lnicola · 2022-03-05T14:07:58Z

It should update automatically, so you don't have to reinstall it. But in the meanwhile you can test a pre-release version by clicking on this button:

(the pre-release versions are generally quite stable)

opensas · 2022-03-05T14:10:05Z

I just went to the second option of this thread and it seems to be working fine.

lnicola · 2022-03-05T14:11:19Z

Yeah, just keep in mind that it won't update automatically and the Code extension and server binary might become mismatched.

xflcx1991 · 2022-03-06T13:08:50Z

It should update automatically, so you don't have to reinstall it. But in the meanwhile you can test a pre-release version by clicking on this button:

(the pre-release versions are generally quite stable)

Done!It seems to working on Ubuntu 18.04 now.But my pre-release version is v0.3.962.

lnicola · 2022-03-06T13:09:54Z

Stable versions are 0.2.X, preview versions are 0.3.Y and source builds are 0.4.0.

taikulawo · 2022-03-07T08:06:51Z

v0.3.963 not working in debian 9

Debian GLIBC 2.24-11+deb9u4

Distributor ID: Debian
Description:    Debian GNU/Linux 9.13 (stretch)
Release:        9.13
Codename:       stretch

/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.963/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /root/.vscode-server/extensions/matklad.rust-analyzer-0.3.963/server/rust-analyzer

lnicola · 2022-03-07T08:08:42Z

The GLIBC version in Debian 9 is too old, you'll have to use rustup as described above. Debian 10 should work.

jotingen · 2022-03-09T15:53:38Z

For Option 2, note that when searching for rust-analyzer.server.path you need to be in the remote tab of settings.

yurymik · 2022-08-22T23:35:23Z

This issue seems to reappear in the most recent release:

~/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1170-linux-x64/server/rust-analyzer --version
rust-analyzer 0.3.1170-standalone (b6d59f2bb 2022-08-14)

~/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer --version
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found

objdump -T ~/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer | grep "GLIBC_2.29"
0000000000000000  w   DF *UND*  0000000000000000  GLIBC_2.29  posix_spawn_file_actions_addchdir_np

This is on Debian 10.12 that has GLIBC 2.28:

~$ cat /etc/issue
Debian GNU/Linux 10 \n \l

$ cat /etc/debian_version
10.12

$ readlink -f /lib/x86_64-linux-gnu/libc.so.6
/usr/lib/x86_64-linux-gnu/libc-2.28.so

lnicola · 2022-08-23T03:08:35Z

@yurymik see #13081.

ponchofiesta · 2022-09-10T13:37:56Z

glibc 2.28 not supported by latest versions anymore.
Last working version with glibc 2.28 is v0.3.1170

zybmajia1 · 2022-09-22T07:13:58Z

why the vscode can not select the version ? downward compatibility is correct。 give up the rust instead of C++。terrible rule.

lnicola · 2022-09-22T07:15:57Z

Since two weeks ago the binaries are built again on Ubuntu 18.04. VS Code different know anything about GLIBC version requirements.

zybmajia1 · 2022-10-13T07:22:54Z

Since two weeks ago the binaries are built again on Ubuntu 18.04. VS Code different know anything about GLIBC version requirements.

If our company use Rust,there are issues:
1.We programe closed type , connect WWW is not allowed. So config enviroment without WWW is impossible.
2.We use linux(run) + windows(vscode & rust-analyzer+Remote - SSH+CodeLLDB) 。 So weekly update is impossible.
Is there offline solution?

wellingfine · 2023-01-31T08:57:25Z

Not found "rust-analyzer.server.path" in v0.4.1387
first install by rustup， then mv to vscode's path：

rustup toolchain install nightly --component rust-analyzer-preview
mv /root/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rust-analyzer /root/.vscode-server/extensions/rust-lang.rust-analyzer-0.4.1387-linux-x64/server/rust-analyzer

manmartgarc · 2023-08-25T16:46:28Z

Looks like the issue should be reopened, still having the exact same issue and the current instructions to edit our VSCode settings are no longer up to date with the extensions' configuration schema.

lnicola · 2023-08-25T17:07:13Z

@manmartgarc which distro are you on? I remember some Ubuntu version upgraded to a newer GLIBC a while ago.

manmartgarc · 2023-08-25T17:17:31Z

@manmartgarc which distro are you on? I remember some Ubuntu version upgraded to a newer GLIBC a while ago.

Using AL2

lnicola · 2023-08-25T17:27:23Z

I suggest building from source for now. The config key is still rust-analyzer.server.path.

people-can-fly · 2023-09-28T20:26:32Z

It works for me in AL2

First make sure the extension is installed.
install the nightly version rustup toolchain install nightly --component rust-analyzer-preview
Note on the previous comment mentioned path of the bin could be different. For my case it was under ASDF
add "rust-analyzer.server.path": "/home/ec2-user/.asdf/installs/rust/1.69.0/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rust-analyzer", to the remote settings.

NoobZang · 2024-04-21T05:50:56Z

git clone https://github.com/rust-analyzer/rust-analyzer
cd rust-analyzer && cargo build --release
cp target/release/rust-analyzer ~/.vscode-server/extensions/rust-lang.rust-analyzer-*version-number*-linux-x64/server/rust-analyzer
But you must recompile rust-analyzer project every time rust-analyzer extension is updated...

jhgg assigned matklad Feb 26, 2022

ceronman mentioned this issue Feb 28, 2022

Unable to run rust-analyzer on Ubuntu 18.04: version `GLIBC_2.29' not found #11584

Closed

This was referenced Feb 28, 2022

vscode Bootstrap error #11583

Closed

Bootstrap error with the latest version. #11586

Closed

ihowell mentioned this issue Mar 1, 2022

Can't work on Ubuntu16.04 #11589

Closed

jhgg changed the title ~~rust-analyzer requires glibc >= 2.28 in pre-release build.~~ rust-analyzer requires glibc >= 2.28 in latest build. Mar 1, 2022

jhgg mentioned this issue Mar 1, 2022

Execute binary failed #11590

Closed

jhgg changed the title ~~rust-analyzer requires glibc >= 2.28 in latest build.~~ "Bootstrap Error" rust-analyzer requires glibc >= 2.28 in latest build. Mar 1, 2022

tysg mentioned this issue Mar 2, 2022

RA bootstrap error #11599

Closed

Veykril unpinned this issue Mar 2, 2022

lnicola mentioned this issue Mar 3, 2022

Format on auto-saving doesn't work #3256

Closed

sylvestre mentioned this issue Mar 4, 2022

Ubuntu cross compilation fails with version GLIBC_2.29 not found uutils/coreutils#3210

Closed

taikulawo mentioned this issue Mar 4, 2022

Overly long loop turn #3959

Closed

zerocity mentioned this issue Mar 25, 2022

Rust-analyzer raises an error when opening a project in WSL2 #10893

Open

JohnnyMorganz mentioned this issue Apr 17, 2022

Statically link linux build JohnnyMorganz/StyLua#444

Closed

lnicola mentioned this issue Aug 23, 2022

2022-08-22 release updated GLIBC version dependency #13081

Closed

"Bootstrap Error" rust-analyzer requires glibc >= 2.28 in latest build. #11558

"Bootstrap Error" rust-analyzer requires glibc >= 2.28 in latest build. #11558

Comments

jhgg commented Feb 26, 2022 • edited Loading

jhgg commented Feb 26, 2022

bjorn3 commented Feb 26, 2022

lnicola commented Feb 26, 2022 • edited Loading

jhgg commented Feb 27, 2022 • edited Loading

bjorn3 commented Feb 27, 2022

bjorn3 commented Feb 27, 2022

jhgg commented Feb 27, 2022 • edited Loading

bjorn3 commented Feb 27, 2022

jhgg commented Feb 27, 2022 • edited Loading

bjorn3 commented Feb 27, 2022

jhgg commented Feb 27, 2022

bjorn3 commented Feb 27, 2022

lnicola commented Feb 27, 2022

taikulawo commented Feb 28, 2022

taikulawo commented Feb 28, 2022 • edited Loading

lnicola commented Feb 28, 2022

Matthias247 commented Feb 28, 2022

rimutaka commented Feb 28, 2022 • edited Loading

Summary of a workaround

Option 1 - downgrade

Notes

Option 2 - use pre-prelease via rustup

Notes

dpypin commented Mar 1, 2022

sunjay commented Mar 1, 2022 • edited Loading

sejr commented Mar 1, 2022

lnicola commented Mar 1, 2022

opensas commented Mar 5, 2022

lnicola commented Mar 5, 2022

opensas commented Mar 5, 2022

lnicola commented Mar 5, 2022

xflcx1991 commented Mar 6, 2022

lnicola commented Mar 6, 2022

taikulawo commented Mar 7, 2022 • edited Loading

lnicola commented Mar 7, 2022 • edited Loading

jotingen commented Mar 9, 2022

yurymik commented Aug 22, 2022

lnicola commented Aug 23, 2022

ponchofiesta commented Sep 10, 2022

zybmajia1 commented Sep 22, 2022

lnicola commented Sep 22, 2022

zybmajia1 commented Oct 13, 2022

wellingfine commented Jan 31, 2023

manmartgarc commented Aug 25, 2023

lnicola commented Aug 25, 2023

manmartgarc commented Aug 25, 2023

lnicola commented Aug 25, 2023

people-can-fly commented Sep 28, 2023

NoobZang commented Apr 21, 2024 • edited Loading

jhgg commented Feb 26, 2022 •

edited

Loading

lnicola commented Feb 26, 2022 •

edited

Loading

jhgg commented Feb 27, 2022 •

edited

Loading

jhgg commented Feb 27, 2022 •

edited

Loading

jhgg commented Feb 27, 2022 •

edited

Loading

taikulawo commented Feb 28, 2022 •

edited

Loading

rimutaka commented Feb 28, 2022 •

edited

Loading

sunjay commented Mar 1, 2022 •

edited

Loading

taikulawo commented Mar 7, 2022 •

edited

Loading

lnicola commented Mar 7, 2022 •

edited

Loading

NoobZang commented Apr 21, 2024 •

edited

Loading