tdx: sgx: Bump DCAP dependency #398
Conversation
Background motivation: Building Trustee on CentOS 9 stream will break, due to an incompatibility of rust-bindgen and clang, as shown by the error below: ``` clang diag: warning: .: 'linker' input unused [-Wunused-command-line-argument] thread 'main' panicked at /home/cloud-user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bindgen-0.60.1/src/ir/context.rs:861:9: "_sgx_ql_qv_supplemental_t_union_(anonymous_at_/usr/x86_64-intel-sgx/include/sgx_qve_header_h_95_5)" is not a valid Ident note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... make: *** [Makefile:22: grpc-as] Error 101 ``` The rust-bindgen version causing this issue was coming from the SGXDataCenterAttestationPrimitives repo. With that in mind, and considering that the DCAP version used so far is 1+ years old, let's bump it and solve those two issues at the same time. Unfortunately, we're also adapting the code a little bit due to the API changes between 1.16 and 1.21. Signed-off-by: Fabiano Fidêncio <[email protected]>
fidencio
force-pushed
the
topic/update-dcap
branch
from
da7041f to
63c02d6
Compare
|
We use Btw when you say updating the container image, which one are you referring to? |
I hope so, but I think we should do the bump there as well and be consistent. WDYT?
Forget about that, I thought that I would also need to update clang / libclang, but that was not needed (and I ended up forgetting to remove the message from the PR). |
It's no longer used to generate the quote. |
Background motivation: Building Trustee on CentOS 9 stream will break, due to an incompatibility of rust-bindgen and clang, as shown by the error below:
The rust-bindgen version causing this issue was coming from the SGXDataCenterAttestationPrimitives repo. With that in mind, and considering that the DCAP version used so far is 1+ years old, let's bump it and solve those two issues at the same time.
Unfortunately, we're also adapting the code a little bit due to the API changes between 1.16 and 1.21.