Zed fails to build on Chimera Linux

[yoctozepto]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

I am trying to build Zed on Chimera Linux. Chimera Linux is a non-GNU Linux distribution, it runs entirely with musl libc and LLVM stack (including their libc++). I have installed the same required packages as suggested for Void Linux (package naming is mostly same between the two). cargo build built all the deps but fails to link the final zed binary. It shows (example with main at 9907742):

  = note: ld: error: undefined symbol: __start_linkme___GPUI_ACTIONS
          >>> referenced by 3pr1xjrb4bjlzugq6x7tejet4
          >>>               gpui-39036a172b51e725.3pr1xjrb4bjlzugq6x7tejet4.rcgu.o:(gpui::action::__GPUI_ACTIONS) in archive /home/radek/src/zed/target/debug/deps/libgpui-39036a172b51e725.rlib
          >>> the encapsulation symbol needs to be retained under --gc-sections properly; consider -z nostart-stop-gc (see https://lld.llvm.org/ELF/start-stop-gc)

          ld: error: undefined symbol: __stop_linkme___GPUI_ACTIONS
          >>> referenced by 3pr1xjrb4bjlzugq6x7tejet4
          >>>               gpui-39036a172b51e725.3pr1xjrb4bjlzugq6x7tejet4.rcgu.o:(gpui::action::__GPUI_ACTIONS) in archive /home/radek/src/zed/target/debug/deps/libgpui-39036a172b51e725.rlib

          ld: error: undefined symbol: __start_linkm2___GPUI_ACTIONS
          >>> referenced by 3pr1xjrb4bjlzugq6x7tejet4
          >>>               gpui-39036a172b51e725.3pr1xjrb4bjlzugq6x7tejet4.rcgu.o:(gpui::action::__GPUI_ACTIONS) in archive /home/radek/src/zed/target/debug/deps/libgpui-39036a172b51e725.rlib
          >>> the encapsulation symbol needs to be retained under --gc-sections properly; consider -z nostart-stop-gc (see https://lld.llvm.org/ELF/start-stop-gc)

          ld: error: undefined symbol: __stop_linkm2___GPUI_ACTIONS
          >>> referenced by 3pr1xjrb4bjlzugq6x7tejet4
          >>>               gpui-39036a172b51e725.3pr1xjrb4bjlzugq6x7tejet4.rcgu.o:(gpui::action::__GPUI_ACTIONS) in archive /home/radek/src/zed/target/debug/deps/libgpui-39036a172b51e725.rlib
          cc: error: linker command failed with exit code 1 (use -v to see invocation)

Relevant software versions (including its Chimera release/build number after the dash, for reference):

LLVM 18.1.8-r6
Rust 1.80.0-r1
Cargo 1.80.0-r0

The same issue happens on main (9907742) and the latest release (v0.146.5).

Environment

(cannot run)

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your Zed.log file to this issue.

No response

[yoctozepto]

Digging deeper, I found:

• "The encapsulation symbol needs to be retained under --gc-sections properly" dtolnay/linkme#49
• rust-lld: error: undefined symbol: __[start|stop]_linkm2_KNOWN_STUBS dtolnay/linkme#94 (open dup of above)

The following workarounds help (choose one):

1. RUSTFLAGS="-Clink-arg=-z -Clink-arg=nostart-stop-gc" (basically implementing what the error message suggests as a workaround)
2. RUSTFLAGS="-C link-dead-code" (hammer-like solution)

[someone13574]

This occurs when building GPUI with the rust nightly toolchain as well. (at least on x86_64 linux). The linker flags work to fix the issue.

[whypet]

Both workarounds have fixed the issue for me partially, I had to disable dynamic linking for musl (#10990) and manually link libunwind as I was getting unresolved symbol errors related to unwinding (not sure why it wasn't already being linked). I added this line above cargo build ... to script/bundle-linux:

export RUSTFLAGS="${RUSTFLAGS} -Clink-arg=-z -Clink-arg=nostart-stop-gc -Ctarget-feature=-crt-static -Clink-args=-lunwind"

The gettext package is needed on Chimera Linux for that bundle script to be able to use envsubst.
I also removed the -d "\n" argument from the xargs command at line 118 because it isn't a valid option in FreeBSD/chimerautils xargs.

[github-actions[bot]]

Hi there! 👋
We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Zed, please let us know by commenting on this issue, and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 7 days.
Thanks for your help!

[ItsHarper]

FWIW, when I'm building on Chimera Linux using cbuild, I no longer find that I need to manually specify any RUSTFLAGS (at least when building Zedless, which will soon no longer depend on LiveKit, and I'm working on adding to cports).