-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when installing from repository on ubuntu 20.04 #15468
Comments
Looks like nobody considered Ubuntu 20.04 when creating the script. I see no Somebody with Ubuntu 20.04 needs to propose changes to that script, otherwise the issue risks staying up ~268 days until 23 April 2025 (Ubuntu 20.04 EOL) and then it will be closed. Alternatively, welcome to use any other means to install those packages in your system, edit the script to omit those and move on. |
The problem is to compile mold in ubuntu 20.04 because of: fatal error: concepts: No such file or directory In ubuntu 20.04 there is no stable repository for "You need a C++20 compiler, like GCC 10.2.0" Any solution ??? |
Keep the old linker and tolerate larger build times? |
I switched to My install script: maysudo=$(command -v sudo || command -v doas || true)
deps=(
gcc
g++
libasound2-dev
libfontconfig-dev
libwayland-dev
libxkbcommon-x11-dev
libssl-dev
libstdc++-10-dev
libzstd-dev
libvulkan1
libgit2-dev
make
clang
curl
jq
gettext-base
elfutils
libsqlite3-dev
)
$maysudo apt-get install -y "${deps[@]}"
#rustup
which rustup > /dev/null 2>&1 || curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
# mold
# which mold > /dev/null 2>&1 || curl -s -L https://github.com/rui314/mold/releases/download/v2.32.1/mold-2.32.1-aarch64-linux.tar.gz | $maysudo tar xvz --strip-components=1 -C /usr/local
which mold > /dev/null 2>&1 || curl -s -L https://github.com/rui314/mold/releases/download/v2.32.1/mold-2.32.1-x86_64-linux.tar.gz | $maysudo tar xvz --strip-components=1 -C /usr/local
which mold
mold --version Then the following worked: cd zed
cargo run -- --help Perhaps someone else with Ubuntu 20.04 on native hardware could test and see if that's enough or whether the graphical bits immediately fail. |
I just tried to build it as well on Ubuntu 20 (before coming across this, and here are some of my notes) From the Linux script, it wasn't able to locate package by regex libstdc++-12-dev, however, it didn't seem to make a difference, as even though I installed the 10-dev one, I ended up uninstalling it and it didn't make an impact. I seemed to have issues with zstd-sys, and ended up running both of these, so I'm not too sure which one it is
I also had a linking error where it couldn't find a certain symbol, and I had to install After that, I was able to build, but got a NoSupportedDeviceFound, which I did find in other issues, and at that point I decided to wait until I upgrade my entire system in a few months and retry. For specs, I'm on Ubuntu 20 (focal), integrated graphics w/ EDIT: said gold instead of mold. Gy bad |
You might try using the backports of mesa drivers for Ubuntu20/22 available in a PPA as described here: #16428 (comment). |
Thank you, that worked. I'll keep the notes I have, and when I go through the process again with a clean box, if I encounter the same errors, I'll be a bit more meticulous and push a PR then to make the install process a bit cleaner. I don't want to clutter up the mess even more if it was just a me-error. |
I'm going to go ahead and close this. We would welcome a PR to improve instructions for building from source on Ubuntu 20.04, but realistically 20.04 is going to be poorly supported by Zed as we approach the April 2025 EOL. Separately, due to GitHub Actions deprecating Ubuntu 20.04 Linux ARM we've been forced to make our Linux ARM builds have a minimum requirement of >=22.04 because of glibc minimum versions. |
Check for existing issues
Describe the bug / provide steps to reproduce it
When executing command line after clone the repository:
Repository commit: 2a649fa
Environment
This is the system:
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.Zed.log
The text was updated successfully, but these errors were encountered: