You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously ring seemed to be the show stopper when compiling boringtun for mipsel targets. Now when I update ring in boringtun to new version 0.17.0, ring and all other boringtun dependencies compile without issue. When it gets to compiling boringtun very last I get.
error[E0432]: unresolved import `std::sync::atomic::AtomicU64`
--> boringtun/src/noise/rate_limiter.rs:8:25
|
8 | use std::sync::atomic::{AtomicU64, Ordering};
| ^^^^^^^^^
| |
| no `AtomicU64` in `sync::atomic`
| help: a similar name exists in the module: `AtomicU8`
Seems like boringtun lacks support for platforms with 32bit pointers. We're so close now, would love see support added for mips.
The text was updated successfully, but these errors were encountered:
Previously ring seemed to be the show stopper when compiling boringtun for mipsel targets. Now when I update ring in boringtun to new version 0.17.0, ring and all other boringtun dependencies compile without issue. When it gets to compiling boringtun very last I get.
Seems like boringtun lacks support for platforms with 32bit pointers. We're so close now, would love see support added for mips.
The text was updated successfully, but these errors were encountered: