Skip to content
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

Time 0.1.41 breaks the build #1235

Closed
armaniferrante opened this issue Dec 13, 2018 · 6 comments
Closed

Time 0.1.41 breaks the build #1235

armaniferrante opened this issue Dec 13, 2018 · 6 comments
Assignees
Labels
c:build Category: build environment p:1 Priority: core feature s:blocked Status: blocked on other work

Comments

@armaniferrante
Copy link
Contributor

time 0.1.41 breaks the build, due to multiple inner modules being defined in sys.rs, when building enclaves.

I suspect this change is responsible time-rs/time@9bdff26, because things only break when we run cargo ekiden build-enclave. For an example, see https://buildkite.com/oasislabs/ekiden/builds/235#_.

As a stopgap, we've pinned the dependency to 0.1.40 in #1233

@kostko kostko added c:build Category: build environment p:1 Priority: core feature labels Jan 1, 2019
@matevz matevz self-assigned this Jan 29, 2019
@matevz
Copy link
Member

matevz commented Jan 29, 2019

It seems a trivial fix is required by upstream in https://github.com/rust-lang-deprecated/time/blob/master/src/sys.rs#L350
#[cfg(unix)] -> #[cfg(all(unix, not(target_env = "sgx")))]
and in https://github.com/rust-lang-deprecated/time/blob/master/src/sys.rs#L690
#[cfg(windows)] -> #[cfg(all(windows, not(target_env = "sgx")))]

Should I make a fork to oasislabs/ org and make PR to upstream?

@matevz
Copy link
Member

matevz commented Jan 30, 2019

Created upstream issue time-rs/time#175

@matevz
Copy link
Member

matevz commented Jan 30, 2019

Created upstream PR: time-rs/time#176
In the mean time, we can use https://github.com/oasislabs/time crate.

@kostko
Copy link
Member

kostko commented Jan 30, 2019

I think we can use the old version for now unless there are changes that we desperately need?

@matevz
Copy link
Member

matevz commented Jan 30, 2019

Yeah, we can just wait for the upstream to fix it. So once time-rs/time#175 is closed, time crate version should be unpinned and this issue closed.

@matevz matevz added the s:blocked Status: blocked on other work label Jan 30, 2019
@kostko
Copy link
Member

kostko commented Feb 2, 2019

I think the correct solution is to use target_vendor = "fortanix", see the following issue rust-lang/rust#57231.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:build Category: build environment p:1 Priority: core feature s:blocked Status: blocked on other work
Projects
None yet
Development

No branches or pull requests

3 participants