Open ARizzo35 opened 3 days ago
this is a bug in https://github.com/mirage/mirage-crypto/issues/216. they use a counter that increments at 24mhz and expect a new value every call.
this is a bug in https://github.com/mirage/mirage-crypto/issues/216. they use a counter that increments at 24mhz and expect a new value every call.
I see...it seems specific to Darwin though? This builds fine on aarch64-linux
.
this is a bug in mirage/mirage-crypto#216. they use a counter that increments at 24mhz and expect a new value every call.
I see...it seems specific to Darwin though? This builds fine on
aarch64-linux
.
AFAIK they both have the issue. apparently the m3 will have a 1GHZ counter. it's possible for the build to succeed by running it a few times. it succeeds on my m2 aarch64-darwin some times. it should probably be marked as broken unless upstream decides it is not an issue for their crypto library.
Steps To Reproduce
Steps to reproduce the behavior:
nix build github:nixos/nixpkgs/nixos-24.11#comby
onaarch64-darwin
Build log
Additional context
nix build github:nixos/nixpkgs/nixos-24.05#comby
succeeds onaarch64-darwin
.Metadata
Notify maintainers
Note for maintainers: Please tag this issue in your PR.
Add a :+1: reaction to issues you find important.