Bitwarden_rs: Package gcc-aarch64-linux-gnu is not available

[DazAh]

Please forgive me if this isn't an issue and I am doing something wrong, complete docker noob here. Anyway when trying to build the docker image for arm using this command:

sudo docker build -t bitwardenarm -f Dockerfile.aarch64 .

The gcc package is not found.
Package gcc-aarch64-linux-gnu is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

[mprasil]

That's weird, the package should be available. However I'm afraid that the build will fail anyways - see #262.

[dani-garcia]

The AArch64 build should be fixed now, can you test if this is still a problem?

[DazAh]

The AArch64 build should be fixed now, can you test if this is still a problem?

Will do.

[DazAh]

@dani-garcia Still compiling... but the dependency was found correctly now thanks.

As mentioned bit of a noob so could be doing something wrong but mine errors out.

note: /app/target/release/deps/libcrypto-59eea2942969070e.rlib(crypto-59eea2942969070e.crypto.5uv3ell8-cgu.10.rcgu.o): In function crypto::util::fixed_time_eq': crypto.5uv3ell8-cgu.10:(.text._ZN6crypto4util13fixed_time_eq17h139f029b759e66d3E+0x18): undefined reference torust_crypto_util_fixed_time_eq_asm'
collect2: error: ld returned 1 exit status

error: aborting due to previous error

error: Could not compile bitwarden_rs.
The command '/bin/sh -c cargo build --release' returned a non-zero code: 101

[dani-garcia]

Weird, I just tried to compile it now and it worked for me. Are you using the latest master? You might need to do git pull to get the latest changes.

[mprasil]

Latest master definitely builds fine - we now have aarch64 image on the docker hub. The error message @DazAh shared sounds like older source code without the disabled yubikey functionality in 1d034749f7b3a0c01d9e32287393498b64f50fde.

[mprasil]

We had couple successful builds for aarch64 since then, I'm going to assume that @DazAh resolved his issue by pulling the latest code and I'm closing the issue, but feel free to reopen if problem still persists.