-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New 1.1.3 breaks older mesalock packages? #282
Comments
hey @Cashmaney , thanks for the report! the reason is that my recommendation is switching back to 2020-04-07, or tell me your exact rust toolchain status and i can create a branch for you. thanks! |
That's the thing - I'm using 2020-04-07, trying to compile with the v1.1.2 sdk, running the exact same compile script inside a docker container that was working a couple of days ago. I suspect hashbrown 0.9.0 doesn't compile with 2020-04-07, and it was added as a dependency when you bumped a few package versions? |
you're right. hashbrown 0.9.0 does not compile on 2020-04-07 and sgx_tstd v1.1.3 does depends on 0.9.0. and v1.1.3 does requires nightly-2020-10-25 or later not only because the change of i just updated the readme. could you please try the new docker images? such as |
We switched to But it's still important to note that when you upgrade, it breaks a lot of the packages that depend on previous versions, since there are some dependencies in packages that are unversioned. For example, |
Hey guys, trying to compile the same code that depended on 1.1.2 now fails
I assume it is because some packages have internal dependencies on 1.1.3, which is compiled with a newer version of rust? After replacing everything I can (without forking packages) to
sgx_1.1.2
my cargo tree now looks like:Just wanted to bring it to your attention, in case you are trying to maintain the 1.1.2 tags as well.
Thanks
The text was updated successfully, but these errors were encountered: