## Description
update old mesatee service name in doc
## How has this been tested?
## Checklist
- [x] Fork the repo and create your branch from `master`.
- [x] If youve added code that should be tested, add tests.
- [x] If youve changed APIs, update the documentation.
- [x] Ensure the tests
The `teaclave_frontend_service` is the output of compilation. Seems that your
building was failed. Can you check if there are service binaries generated in
the `release/services/` direactory?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
Hello,
I had built Teaclave in simulation mode
`docker run --rm -v $(pwd):/teaclave -w /teaclave \
-it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
bash -c ". /root/.cargo/env && \
. /opt/sgxsdk/environment && \
mkdir -p build && cd build && \
cmake -DTEST_MODE=ON
Nice catch! Thank you.
--
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/pull/436#issuecomment-737595466
Merged #436 into master.
--
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/pull/436#event-4065087557
## Description
`libcurl4-openssldev` is a typo of `libcurl4-openssl-dev`-
https://packages.debian.org/jessie/libcurl4-openssl-dev
Fixes # (issue)
Use the right spelling
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
-
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/295
--
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-sgx-sdk/issues/294#issuecomment-737478711
this would help people who have Intel SDK installed at `/opt/intel/sgxsdk` and
do not set `SGX_SDK`
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/295
-- Commit Summary --
* compile: probe sgx sdk in opt intel
> and we always use `/opt/intel/sgxsdk` as a symlink to the desired release
do an `export SGX_SDK=/opt/intel/sgxsdk` before `make` and try again. if it
works, i'll update rust sgx sdk immediately for you. and you'll not need to
export that again.
--
You are receiving this because you are
and we always use `/opt/intel/sgxsdk` as a symlink to the desired release
--
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-sgx-sdk/issues/294#issuecomment-73749
thanks a lot for reproducing. I will try again with cargo update
--
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-sgx-sdk/issues/294#issuecomment-737466082
or i can probe both `/opt/sgxsdk` and `/opt/intel/sgxsdk` in build.rs :-)
that'll make you convenient! give me a minute!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> anyway, I have a temporary fix for the `sgx_trts.h` error by just updating
> log-sgx with `cargo update -p log` and then manually fix Cargo.lock to match
> all commits to be
> [254368b](https://github.com/apache/incubator-teaclave-sgx-sdk/commit/254368badb9eb2d4cdab631a34e234bf6e54e585)
>
@brenzi i can confirm that on docker container `baiduxlab/sgx-rust` it can
build after cargo update
```
docker run -ti --rm baiduxlab/sgx-rust:1804-1.1.3 bash
```
```
rustup target add wasm32-unknown-unknown
git clone https://github.com/encointer/encointer-worker.git
cd encointer-worker
wget
@brenzi suddenly i realized that it may caused by recent changes on search path
of Intel SDK. where did you installed your sdk? `/opt/sgxsdk/` or
`/opt/intel/sgxsdk`?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
anyway, I have a temporary fix by just updating log-sgx with `cargo update -p
log`. Still, this is a brittle situation because the build won't work anymore
after a `cargo update`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
@dingelish it seems that `make clean` doesn't help neither.
I see that you have retagged 1.1.3 to include support for newer compiler (the
old tag pointed to 254368badb9eb2d4cdab631a34e234bf6e54e585). I think
re-tagging is a dangerous practise if you have other repos depending on yours.
Why not
17 matches
Mail list logo
