-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Issues building for void-linux #7958
Comments
Actually, why do you want the third_party folder? It shouldn't be required for building Deno. |
In this case I don't need it. Thought it is required because my build always failes. Background: Try to package it for the Void linux distribution. May you help me whats going wrong? Here is the Travis CI build log: https://travis-ci.org/github/void-linux/void-packages/builds/735400951 |
I think this distro only ships with musl right? Deno requires glibc right now. See #3711 Also Deno does not support i686. |
Not it ships with glibc too! This isn't the problem becsuse I can skip the musl builds. But it even doesn't build on glibc. |
The minimum supported rust version is 1.46.0. It seems your release is older. Also you need a very recent version of clang: https://github.com/denoland/rusty_v8#build-v8-from-source |
Oh okay this may be the cause. I will give it a try. Thanks for your help! |
As far as I see void
Where did you see that? As far as I see Voidlinux uses version 1.46.0: https://github.com/void-linux/void-packages/blob/master/srcpkgs/rust/template#L7
LLVM 10.0 works too, right? (https://github.com/void-linux/void-packages/blob/master/srcpkgs/llvm/template#L3) |
LLVM is a compiler backend, and not the same as something like gcc or clang (which is the compiler frontend that parses c / c++ and translates it LLVM IR). rusty_v8 hasnt been built with anything other than recent clang for a long time, so anything else (like gcc) likely won't work. |
Note that rusty_v8 will actually download clang automatically so it should "just work". |
Thanks @lucacasonato and @piscisaureus for your great explanations and help. I really appreciate it! Actually I guess the problem has something to do with gn because of this error log:
I gonna investigate further. Love deno and want it be packaged on Voidlinux. |
gn should also be automatically installed though. I wonder if you’re on a 32 bit system. We don’t support 32 bit builds. |
hmm okay
Voidlinux supports many archs: x86_64, i686, aarch64, armv7l, armv6l and all for glibc and musl libc. I can't build deno on any... even x86_64 glibc. Have a look at: https://travis-ci.org/github/void-linux/void-packages/builds/735400951 |
Gn is typically downloaded by the cargo_gn crate somewhere into the build directory. |
Oh okay I used https://gn.googlesource.com/gn |
How can I prevent fetching precompiled binaries during build process? See: void-linux/void-packages#22043 (comment) and void-linux/void-packages#25436 (comment) |
Any progress on this? |
There is nothing actionable here. If you are still struggling with building Deno from source, please open a new issue. |
After unpacking a release tarball (e.g. 1.4.6) the third_party folder is empty. Guess the step https://github.com/denoland/deno/blob/master/.github/workflows/ci.yml#L61 needs to be updated...
The text was updated successfully, but these errors were encountered: