After investigation, I think I find the root cause. This isn't the code bug. It
should be caused by the GitHub network connection issue within mainland in
China. The vendored third-party crates failed to be fully updated.
--
You are receiving this because you are subscribed to this thread.
Closed #499.
--
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/issues/499#event-4751029608
We only use vendored third-party crates. Therefore, any upstream
changes/updates won't affect our build process.
Did you change anything with the building system?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Hi, thanks for your report. I cannot reproduce your issue.
>
> Basically, I followed your steps and built Teaclave successfully.
hi, thanks for your response.
I checked https://crates.io/crates/sgx_rand/versions and found that there is no
1.1.2 version and the latest version is 1.1.1.
Looks
hi, thanks for your response.
I checked https://crates.io/crates/sgx_rand/versions and found that there is no
1.1.2 version and the latest version is 1.1.1.
Looks like that's the reason why it failed. Isn't it?
--
You are receiving this because you are subscribed to this thread.
Reply to this
Hi, thanks for your report. I cannot reproduce your issue.
Basically, I followed your steps and built Teaclave successfully.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I tried to build the Teaclave platform using docker with the -DSGX_SIM_MODE=ON
option
```
$ git clone https://github.com/apache/incubator-teaclave.git
$ cd incubator-teaclave
$ docker run --rm -v $(pwd):/teaclave -w /teaclave \
-it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
bash
