Closed nachoguru closed 4 years ago
Let me know if there's anything I can do to help you test or diagnose.
In case these are helpful:
Output of uname -srm
is:
Linux 5.4.0-26-generic x86_64
Output of lsb_release -a
is:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
apt-get install make
...and we're in business! cargo install fd-find
ran fine after that.
Thank you @sfackler
apt-get install make
it solve my problem, too. thank you very much.
apt-get install make
Thank you. It also solves my problem when compiling solana on ubuntu/aarch64:
--- stderr thread 'main' panicked at 'failed to execute command: No such file or directory (os error 2)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tikv-jemalloc-sys-0.4.2+5.2.1-patched.2/build.rs:329:19
apt-get install make
This also solves the issue when installing LunarVim on Arch Linux under WSL, albeit it is sudo pacman -S make
Not directly related to issue. I was trying to build a substrate-node on my Windows 11 machine using WSL 2.0. The build for tikv-jemalloc-sys-0.4.3+5.2.1-patched.2 always failed.
To resolve the issue, I had to run:
sudo apt install make
I'm not a Rust or C++ programmer, I just use a few tools written in Rust. One of them (fd-find) depends on jemallocator ^0.3.0 and does not build on a new Ubuntu 20.04 LTS VM on Digital Ocean.
Not sure if this is just a Digital Ocean thing, or just an Ubuntu 20.04 thing, or something new in Linux kernel 5.4.0 but I thought I would at least report it in case it is useful to you.
When I ran my usual cargo install of handy command line tools:
...everything installed except
fd-find
, which died here: