Open celaus opened 2 years ago
@celaus which rustc are you using? i just tested against nightly-2021-11-01 and didn't reproduce.
$ rustc --version rustc 1.58.0-nightly (ff0e14829 2021-10-31)
I was using the respective docker images for each compile:
$ sudo docker run -ti -v (pwd):/root/sgx --device /dev/isgx baiduxlab/sgx-rust:1804-1.1.4 bash
root@23e62148b04d:~# rustc --version
rustc 1.58.0-nightly (ff0e14829 2021-10-31)
and
$ sudo docker run -ti -v (pwd):/root/sgx --device /dev/isgx baiduxlab/sgx-rust:1804-1.1.3 bash
root@e8f1676b3dde:~# rustc --version
rustc 1.49.0-nightly (ffa2e7ae8 2020-10-24)
root@e8f1676b3dde:~#
@celaus reproduced. thanks!
looks like the newer compiler somehow does not include __assert_fail
's implementation in generated static libraries. to this end, you can export CFLAGS="-DRING_CORE_NOSTDLIBINC=1"
to let Ring build without the __assert_fail
dependency.
Hi,
it looks like something changed between 1.1.3 and 1.1.4 that keeps ring (and I assume other dependencies with a
debug_assert
) from building. Here is the log output, note that I commented out the release flag in the enclave's build file (cargo build #--release
). At the end of the log you'll find the corresponding linker error:Whereas the same thing works in 1.1.3 (here it's just
cargo build
):Can you check what happened?