volcano

@haerdib I will upgrade rust-toolchain again recently to support rust `edition 2021`.

@PiDelport `v1.1.4-testing` can support `intel sgx sdk 2.15.1` and `dcap 1.12.1` `v1.1.4-testing` has been merged into `master`

@haerdib I have upgraded rust-toolchain to `nightly-2021-11-01.`

@PiDelport This issue has been resolved.

The`edl/`folder is legacy, I will remove it in a later version.

- rust sgx sdk v1.1.2 supports rust nightly-2020-04-07. - rust sgx sdk on longer supported rust-stable after v1.0.8. - Add feature(rustc_private) to your enclave::lib.rs. #![cfg_attr(all(target_env = "sgx", target_vendor = "mesalock"),...

@reuvenpo You can try to use -Z force-unstable-if-unmarked flag to solve your problem. This flag forces the crate to be unstable, while also allowing them to use other "unstable" crates....

My verification result is that after using the -Z force-unstable-if-unmarked flag, you do not need to set rustc_private for your crate and all crates it depends on.

Yes, I also see that there is no mention of any information about this flag(force-unstable-if-unmarked) in the xargo doc, so this issue still needs analysis. If there is any progress,...

The issue is because crates in SGX custom sysroot do not declare # [staged_api] and # [stable] features. If set the -Z force-unstable-if-unmarked flag, rustc will automatically mark rustc_private features,...