[WIP] Arm64/Aarch64 ci builds

[sunsetkookaburra]

Will create a PR when I have this working and cleaned up, at the moment the repo-history is a mess. Utilising some of the work from rusty_v8's arm 64 ci.yml done by afinch7. I'm trying out a community gh-action that allows running on non-intel cpus by utilising docker. I'm also looking into cargo runners, which I think provide the list of executables which can be stored and run on this docker instance. 🤞

[sunsetkookaburra]

i'm somewhat close after two solid days of head scratching. i ran a built debug version on a RPi3 and got an error relating to V8.
here's my work so far https://github.com/sunsetkookaburra/deno/tree/arm64_ci
main problem now is that the github actions instance runs out of space when building it as debug

[sunsetkookaburra]

Feeling like I've hit somewhat of a dead end myself, and don't know enough about rust and the build process to do this justice. Passing this on to whoever wants to work on this.
I've come close with sunsetkookaburra/deno@b09ef29 and with sunsetkookaburra/deno@a248afb

[sunsetkookaburra]

This image shows the result when running the aarch64 target binary on Ubuntu 18.04LTS on a RPi3, AARCH64

for anyone who knows something about linux binary builds:

this is at sunsetkookaburra/deno@f0249dd

[sunsetkookaburra]

if it helps, deno --version and deno help are able to run successfuly.

[sunsetkookaburra]

(for my reference, first round of attempts: sunsetkookaburra/deno@2ef273a)

[afinch7]

If you can get v8 to compile successfully the only other major issue you are going to run into is snapshots. Snapshots generated using a x86 compiles of v8 are not compatible with arm compiles of v8. It took me a long time to figure this out the first time around, but It makes more sense when you realize that a snapshot is mostly compiled bytecode from v8's JIT compiler. The only solution I managed to get working here is just don't use snapshots for arm builds, but I would be happier if we could generate arm snapshots.

[sunsetkookaburra]

I did try (at one point) forcing it to build v8 (on arm), and that didnt work.

[ktfth]

How can i reproduce that kind of behavior on my setup? Or this just can be reproduced on the CI?

[sunsetkookaburra]

@ktfth this was trying to build using the ci, but following the steps for aarch64 on your machine should do much the same. Rust-Cross looks promising, but I couldn't figure out how to install python in that image or rust, it also needs docker installed locally.

Rust cross (https://github.com/rust-embedded/cross) is so close to an answer I feel, you just need to figure out installing the build tools onto that image (rust+python+...)

[ktfth]

Running the following command "cross build --target aarch64-unknown-linux-gnu"

I have getted the output:

error: failed to run custom build command for rusty_v8 v0.4.2

Caused by:
process didn't exit successfully: /target/debug/build/rusty_v8-a9c2e62a39932a56/build-script-build (exit code: 101)
--- stdout
static lib URL: https://github.com/denoland/rusty_v8/releases/download/v0.4.2/librusty_v8_debug_aarch64-unknown-linux-gnu.a
cargo:rustc-link-search=/target/aarch64-unknown-linux-gnu/debug/gn_out/obj
Downloading https://github.com/denoland/rusty_v8/releases/download/v0.4.2/librusty_v8_debug_aarch64-unknown-linux-gnu.a

--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /cargo/registry/src/github.com-1ecc6299db9ec823/rusty_v8-0.4.2/build.rs:221:18
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

warning: build failed, waiting for other jobs to finish...
error: build failed

You have passed this step?

[sunsetkookaburra]

@ktfth I did manage to. I used docker run -v /host/directory:/container/directory to map the repo inside the root of the docker container, but I don't think with rust cross.
So if you can find another way to add the folder (ADD command in a custom dockerfile for rust-cross I think) that should get you further along.

I used this dockerfile with rust-cross: (I didn't try using ADD)

FROM rustembedded/cross:aarch64-unknown-linux-gnu-0.2.0
RUN apt update && apt install -yq --no-install-suggests --no-install-recommends python && ls /usr/bin

[ktfth]

It's a good place to put docker file on the project?

https://github.com/ktfth/deno/blob/feature/aarch64/Dockerfile

[ktfth]

I have updated the docker file to act as multi-stage and work well now i need to solve that part.

error: failed to parse manifest at /deno/cli/Cargo.toml

Caused by:
the default-run manifest key is unstable

Caused by:
feature default-run is required

this Cargo does not support nightly features, but if you
switch to nightly channel you can add
cargo-features = ["default-run"] to enable this feature

Have any tip for that?