Bottles for navi and cargo(from rust) on ubuntu 64 seem to be corrupted #2920
Answered
by
Bo98
aaronliu0130
asked this question in
Everyday usage
-
I'm running ubuntu WSL on a 64bit Windows computer. When I install navi and cargo from bottle, I get an /home/linuxbrew/.linuxbrew/Cellar/navi/2.19.0/bin/navi: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /home/linuxbrew/.linuxbrew/lib/ld.so, for GNU/Linux 2.6.32, BuildID[sha1]=9fb6e7d762db39be2eb1a21a7abbe88db2245c3e, not stripped
/home/linuxbrew/.linuxbrew/Cellar/rust/1.58.1/bin/cargo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /home/linuxbrew/.linuxbrew/lib/ld.so, for GNU/Linux 2.6.32, BuildID[sha1]=ada7c7f73bb88ccddd6dab856931c72998279f4c, not stripped
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
ilmbase
HOMEBREW_VERSION: 3.3.13-44-g8e97f60
ORIGIN: http://github.com/Homebrew/brew
HEAD: 8e97f608581e83681c83c1ee9f4257a8bb703e19
Last commit: 3 days ago
Core tap ORIGIN: http://github.com/Homebrew/homebrew-core
Core tap HEAD: f35c70b345f6c40f39133cf01f0571f44da487ee
Core tap last commit: 2 days ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_CURLRC: set
HOMEBREW_EDITOR: nano
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/bin/ruby
CPU: octa-core 64-bit skylake
Clang: N/A
Git: 2.17.1 => /usr/bin/git
Curl: 7.81.0 => /usr/bin/curl
Kernel: Linux 4.4.0-18362-Microsoft x86_64 GNU/Linux
OS: Ubuntu 18.04.5 LTS (bionic)
Host glibc: 2.27
/usr/bin/gcc: 7.5.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@5: N/A
xorg: N/A |
Beta Was this translation helpful? Give feedback.
Answered by
Bo98
Feb 5, 2022
Replies: 1 comment
-
There are known issues with WSL1 you may be hitting (like microsoft/WSL#5875). Are you able to use WSL2 instead? That should work much better. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
aaronliu0130
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are known issues with WSL1 you may be hitting (like microsoft/WSL#5875).
Are you able to use WSL2 instead? That should work much better.