Off the top of my head, we've seen it getting triggered by lazy_static in our
dependencies.
Looking at conversation logs i found this as well:
```
error[E0658]: use of unstable library feature 'rustc_private': this crate is
being loaded from the sysroot, an unstable location; did you mean to load this
crate from crates.io via `Cargo.toml` instead?
-->
/home/username/.cargo/registry/src/github.com-1ecc6299db9ec823/secp256k1-sys-0.1.2/src/lib.rs:301:5
|
301 | assert!(mem::align_of::<usize>() >= mem::align_of::<u8>());
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #27812 <https://github.com/rust-lang/rust/issues/27812>
for more information
= help: add `#![feature(rustc_private)]` to the crate attributes to enable
= note: this error originates in a macro (in Nightly builds, run with -Z
macro-backtrace for more info)
error: aborting due to previous error
For more information about this error, try `rustc --explain E0658`.
error: could not compile `secp256k1-sys`.
To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/231#issuecomment-621713207
