proc macro `Deserialize` not expanded: Cannot create expander for libserde_derive: UnsupportedABI

[msvi]

rust-analyzer version: 0.3.1277-standalone

rustc version: 1.65.0 (897e37553 2022-11-02)

relevant settings: --

rustup show:

Default host: x86_64-unknown-linux-gnu
rustup home:  $HOME/.rustup

stable-x86_64-unknown-linux-gnu (default)
rustc 1.65.0 (897e37553 2022-11-02)

I'm getting the following error message with serde:

proc macro `Deserialize` not expanded: Cannot create expander for <project>/target/debug/deps/libserde_derive-a150df8d26d00fd1.so: UnsupportedABI

I've already cleaned and recompiled the project. Building and cargo check works fine.

[lnicola]

Strange, do you have ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/libexec/rust-analyzer-proc-macro-srv? Does your project have a rust-toolchain file?

[bjorn3]

And what does readelf --hex-dump .rustc <project>/target/debug/deps/libserde_derive-a150df8d26d00fd1.so | head show?

[Veykril]

I think we should try and make that error message more helpful by printing expected abi vs found one etc.

[msvi]

Strange, do you have ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/libexec/rust-analyzer-proc-macro-srv? Does your project have a rust-toolchain file?

Yes, that file exists. I don't have a rust-toolchain file in my project.

And what does readelf --hex-dump .rustc <project>/target/debug/deps/libserde_derive-a150df8d26d00fd1.so | head show?

Hex dump of section '.rustc':
  0x00000000 72757374 00000006 ff060000 734e6150 rust........sNaP
  0x00000010 705900ed 1d004c9c 489f8080 04307275 pY....L.H....0ru
  0x00000020 73740000 00060002 2cf62901 0d506320 st......,.)..Pc 
  0x00000030 312e3635 2e302028 41726368 204c696e 1.65.0 (Arch Lin
  0x00000040 75782001 19082031 3a091a70 2d3129c1 ux ... 1:..p-1).
  0x00000050 00000001 00060010 64657269 76655f73 ........derive_s
  0x00000060 65726961 6c697a65 c1051700 120d1704 erialize........
  0x00000070 64651d19 c00000e9 09ea0900 00008018 de..............

[bjorn3]

Looks like your project is compiled with a rustc installed from the arch linux package repos. This version is incompatible with a rustc from rustup. Does /usr/libexec/rust-analyzer-proc-macro-srv exist? If so rust-analyzer probably gets confused and thinks it needs to load the rust-analyzer-proc-macro-srv from rustup. If not rust-analyzer may have picked the right rustc, but fails anyway as arch linux doesn't ship the proc macro server. In either case compiling using the rustup distributed version of rustc (by putting ~/.cargo/bin before /usr/bin in your PATH or by removing the arch linux installed rustc) should solve your issues.

[lnicola]

Arch has /usr/lib/rust-analyzer-proc-macro-srv. But indeed, you should uninstall the Arch rust package.

[bjorn3]

This is the issue: https://github.com/archlinux/svntogit-packages/blob/packages/rust/trunk/0001-bootstrap-Change-libexec-dir.patch Arch linux decided to move rust-analyzer-proc-macro-srv from libexec to lib, breaking rust-analyzer. @heftig why does arch linux change libexec to lib for rust-analyzer-proc-macro-srv?

[lnicola]

Arch doesn't have a /usr/libexec at all.

[msvi]

Thank you very much everyone for your help. After removing the system rustc installation the issue is resolved.

However, I had ~/.cargo/bin as highest priority in my PATH (set in ~/.zshenv) and /usr/lib/rust-analyzer-proc-macro-srv did exist.

[lnicola]

and /usr/lib/rust-analyzer-proc-macro-srv did exist

We build the path to that executable by appending libexec to the output of rustc --print sysroot. The latter is /usr on Arch.

[heftig]

@heftig why does arch linux change libexec to lib for rust-analyzer-proc-macro-srv?

Arch Linux never had /usr/libexec/ and to install files there is a packaging error. Binaries that should be in PATH are installed into /usr/bin/ and those that don't are installed into /usr/lib/. All packages use /usr/lib/ or a subdirectory as the libexecdir.

[lnicola]

I'd be in favour of us trying both libexec and lib for better compatibility.

[bjorn3]

@heftig I see. I guess we could move it to lib/rustlib/x86_64-unknown-linux-gnu/libexec (or .../bin). In any case it would have been nice if you informed us about the incompatibility with the arch linux packaging rules. The sole purpose of rust-analyzer-proc-macro-srv is to make any (recent) rust-analyzer version (including those distributed in the vscode extension) work with with any (recent) rustc version independent of who built it. This requires at a minimum a well known location that is independent of the entity packaging rust or rust-analyzer. Had we known that arch linux doesn't allow /usr/libexec, I'm sure we would have chosen a location that does work for everyone involved.

[nozwock]

#13589 (comment)
Thanks, I resolved the issue by removing the Arch rust pkg.

by putting ~/.cargo/bin before /usr/bin in your PATH or by removing the arch linux installed rustc

I already had ~/.cargo/bin before /usr/bin in my PATH, but still encountered this issue, weird?

btw I was sure I had rust pkg removed before, maybe some AUR pkg installed it for builds and I didn't pay attention.

[bjorn3]

Is it also this way for your editor? (you can use cat /proc/<editor pid>/environ | tr '\0' '\n' to show all env vars set for your editor) ~/.zshenv is only read by zsh afaik and not when logging in on a graphical system. And as such your editor likely doesn't inherit the env vars set in ~/.zshenv. ~/.profile is the shell script that runs when logging in.