[GH-ISSUE #622] armv7 build issues #419

New issue

Closed

opened 2026-03-03 01:28:56 +03:00 by kerem · 3 comments

kerem commented 2026-03-03 01:28:56 +03:00

Owner

Copy link

Originally created by @mqus on GitHub (Sep 13, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/622

This issue is likely not because of bitwarden_rs but an issue of the nightly rust compiler, but I want to track it here in case someone encounters it. I'll probably close it as soon as I think that it's fixed. If you think that this is just a useless duplicate, you can also close it, I just want to document it somewhere.

On a RasPi 3 with ArchlinuxARM installed (armv7h) I got the following errors while building the AUR package (release 1.10):

   Compiling libc v0.2.62
   Compiling autocfg v0.1.5
   Compiling semver-parser v0.7.0
   Compiling rand_core v0.4.2
error: Could not compile `rand_core`.

Caused by:
  process didn't exit successfully: `rustc --crate-name rand_core /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/rand_core-0.4.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 --cfg 'feature="alloc"' --cfg 'feature="std"' -C metadata=312a6abff637b24a -C extra-filename=-312a6abff637b24a --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference)
warning: build failed, waiting for other jobs to finish...
error: Could not compile `libc`.

Caused by:
  process didn't exit successfully: `rustc --crate-name build_script_build /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.62/build.rs --color always --crate-type bin --emit=dep-info,link -C opt-level=3 --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=e02a73bca267324a -C extra-filename=-e02a73bca267324a --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/build/libc-e02a73bca267324a -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference)
warning: build failed, waiting for other jobs to finish...
error: Could not compile `semver-parser`.

Caused by:
  process didn't exit successfully: `rustc --crate-name semver_parser /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/semver-parser-0.7.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C metadata=c0a4b0d5e47e0bcf -C extra-filename=-c0a4b0d5e47e0bcf --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference)
warning: build failed, waiting for other jobs to finish...
error: Could not compile `autocfg`.

Caused by:
  process didn't exit successfully: `rustc --crate-name autocfg /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/autocfg-0.1.5/src/lib.rs --color always --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C metadata=db8ac9546e1eae17 -C extra-filename=-db8ac9546e1eae17 --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference)

This looks a lot like https://github.com/rust-lang/rust/issues/62896 .

I worked around it by simply changing the content of the file rust-toolchain to an older toolchain (in my case nightly-2019-05-11, the toolchain of the 1.9.1 release).
I had no issues compiling after that so it seems to work.

PS: Added the bitwarden_rs version (1.10)

Originally created by @mqus on GitHub (Sep 13, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/622 This issue is likely not because of bitwarden_rs but an issue of the nightly rust compiler, but I want to track it here in case someone encounters it. I'll probably close it as soon as I think that it's fixed. If you think that this is just a useless duplicate, you can also close it, I just want to document it somewhere. On a RasPi 3 with ArchlinuxARM installed (armv7h) I got the following errors while building the AUR package (release 1.10): ``` Compiling libc v0.2.62 Compiling autocfg v0.1.5 Compiling semver-parser v0.7.0 Compiling rand_core v0.4.2 error: Could not compile `rand_core`. Caused by: process didn't exit successfully: `rustc --crate-name rand_core /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/rand_core-0.4.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 --cfg 'feature="alloc"' --cfg 'feature="std"' -C metadata=312a6abff637b24a -C extra-filename=-312a6abff637b24a --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference) warning: build failed, waiting for other jobs to finish... error: Could not compile `libc`. Caused by: process didn't exit successfully: `rustc --crate-name build_script_build /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.62/build.rs --color always --crate-type bin --emit=dep-info,link -C opt-level=3 --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=e02a73bca267324a -C extra-filename=-e02a73bca267324a --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/build/libc-e02a73bca267324a -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference) warning: build failed, waiting for other jobs to finish... error: Could not compile `semver-parser`. Caused by: process didn't exit successfully: `rustc --crate-name semver_parser /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/semver-parser-0.7.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C metadata=c0a4b0d5e47e0bcf -C extra-filename=-c0a4b0d5e47e0bcf --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference) warning: build failed, waiting for other jobs to finish... error: Could not compile `autocfg`. Caused by: process didn't exit successfully: `rustc --crate-name autocfg /home/mqs/.cargo/registry/src/github.com-1ecc6299db9ec823/autocfg-0.1.5/src/lib.rs --color always --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C metadata=db8ac9546e1eae17 -C extra-filename=-db8ac9546e1eae17 --out-dir /home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps -L dependency=/home/mqs/.cache/yay/bitwarden_rs/src/bitwarden_rs-1.10.0/target/release/deps --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference) ``` This looks a lot like https://github.com/rust-lang/rust/issues/62896 . I worked around it by simply changing the content of the file `rust-toolchain` to an older toolchain (in my case `nightly-2019-05-11`, the toolchain of the 1.9.1 release). I had no issues compiling after that so it seems to work. PS: Added the bitwarden_rs version (1.10)

kerem closed this issue 2026-03-03 01:28:56 +03:00

kerem commented 2026-03-03 01:28:57 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Sep 15, 2019):

Yeah, we've had this issue turn up a couple of time with different hardware and software configurations so far, we should possibly consider rolling back the rust-toolchain file until the issue is resolved.

<!-- gh-comment-id:531591964 --> @dani-garcia commented on GitHub (Sep 15, 2019): Yeah, we've had this issue turn up a couple of time with different hardware and software configurations so far, we should possibly consider rolling back the rust-toolchain file until the issue is resolved.

kerem commented 2026-03-03 01:28:57 +03:00

Author

Owner

Copy link

@mqus commented on GitHub (Oct 21, 2019):

The referenced bug was fixed and I just successfully compiled bitwarden_rs with the 2019-10-21 nightly toolchain (nightly-2019-10-21-armv7-unknown-linux-gnueabihf)on a raspberry pi (armv7h).

This issue can be closed as soon as rust-toolchain is updated.

<!-- gh-comment-id:544725095 --> @mqus commented on GitHub (Oct 21, 2019): The referenced bug was fixed and I just successfully compiled bitwarden_rs with the 2019-10-21 nightly toolchain (`nightly-2019-10-21-armv7-unknown-linux-gnueabihf`)on a raspberry pi (armv7h). This issue can be closed as soon as `rust-toolchain` is updated.

kerem commented 2026-03-03 01:28:57 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Oct 22, 2019):

#679 should resolve this

<!-- gh-comment-id:545024825 --> @mprasil commented on GitHub (Oct 22, 2019): #679 should resolve this

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels   

SSO

  

Third party

  

better for forum

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

future Vault

  

future Vault

  

future Vault

  

good first issue

  

help wanted

  

low priority

  

notes

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

troubleshooting

  

wontfix

No labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

question

troubleshooting

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vaultwarden#419

No description provided.