DemesneGH commented on issue #240:
URL: 
https://github.com/apache/teaclave-trustzone-sdk/issues/240#issuecomment-3420373326

   For the problem 1:
   
   > Should we officially bump the toolchain version in the repository to 
nightly ≥ 2024-09-01 to maintain compatibility with indexmap and related crates?
   
   For CA and no-std TAs we can easily bump the Rustc version, but for std TAs, 
since we have manually pinned it to the `2024-05-14` and ported the Rust source 
code to add OP-TEE building target, we cannot bump this version right now.
   Because the `rust-toolchain.toml` is shared between all CAs, no-std TAs and 
std TAs, even if upgrading version fix the issue for CA, changing the Rustc 
version will cause the std TAs building failed.
   
   To upgrade the rustc for std TAs, we can (1) manually port the Rust source 
code like what we did in the previous version (ref: 
https://github.com/apache/teaclave-trustzone-sdk/blob/main/setup_std_dependencies.sh);
 (2) upstream the OP-TEE target into the Rust main source then we don't need 
manually port anymore. I'm planning to try the approach 2.
   
   Once we upgrading the rustc version for std TAs we can bump this version in 
`rust-toolchain.toml`.
   
   > indexmap v2.12.0 explicitly requires rustc ≥ 1.82.
   
   As a temporary workaround, you can pin the indexmap version in the 
optee-teec Cargo.toml without upgrading rustc version, such as: 
https://github.com/apache/teaclave-trustzone-sdk/blob/main/optee-teec/macros/Cargo.toml#L34-L39
   
   If it works please feel free to open a PR.
   
   ----
   For the problem2:
   
   If the problem 1 resolved, please retry the std build and give a full detail 
of the commands to reproduce this issue, thanks!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to