You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With tokio 1.20.1 it was possible to build for the x86_64-fortanix-unknown-sgx target when not using the net feature since the socket2 dependency was optional and only enabled when net was enabled. With tokio 1.21.0 compilation now fails due to socket2 being required and built with the all feature flag which is not supported on the x86_64-fortanix-unknown-sgx target.
Could socket2 be removed as a dependency on x86_64-fortanix-unknown-sgx similar to how it is now on wasm* targets or if there is another course of action that would be more suitable to ensure compilation on x86_64-fortanix-unknown-sgx?
The text was updated successfully, but these errors were encountered:
Sure, just opened #5001 (need to test if it works on CI after the workflow gets approved). The test is just a simple build test as actually running some unit tests requires SGX hardware (and therefore some custom GitHub runners).
With tokio 1.20.1 it was possible to build for the
x86_64-fortanix-unknown-sgx
target when not using thenet
feature since thesocket2
dependency was optional and only enabled whennet
was enabled. Withtokio 1.21.0
compilation now fails due tosocket2
being required and built with theall
feature flag which is not supported on thex86_64-fortanix-unknown-sgx
target.Could
socket2
be removed as a dependency onx86_64-fortanix-unknown-sgx
similar to how it is now onwasm*
targets or if there is another course of action that would be more suitable to ensure compilation onx86_64-fortanix-unknown-sgx
?The text was updated successfully, but these errors were encountered: