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
Disable clock_getres on redox #1327
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please explain why, and also add an entry to CHANGELOG?
Should I explain why as a comment in the code, or just here? If the latter, it's because |
Except that it doesn't fail. We build for Redox in CI. Why does that pass, but whatever you're doing does not? |
Huh, really? Weird... here's the error I get:
|
I guess I'm building under redoxer, whereas CI builds just using cross-compilation. |
It's strange though, because
|
Nope, it's our mistake. There's an error in the Travis file. Could you please add this to your PR? --- a/.travis.yml
+++ b/.travis.yml
@@ -104,7 +104,7 @@ matrix:
- curl --proto '=https' --tlsv1.2 -sSf --output rustup.sh https://sh.rustup.rs
- sh rustup.sh -y --profile=minimal --default-toolchain 1.36.0 --target x86_64-unknown-redox
- . $HOME/.cargo/env
- - cargo build --all-targets
+ - cargo build --target x86_64-unknown-redox --all-targets
before_install: set -e |
You'll have to rebase to fix the CI errors, not to mention the merge conflict. |
36be25b
to
96f6581
Compare
@coolreader18 did you notice the build failures for Redox? I think you'll have to switch Redox's compiler to nightly. libc seems to require it. |
Ah, alright |
96f6581
to
21c1f41
Compare
Since Travis has been working so poorly this week, I'm working on replacing it. I've pulled your changes into PR #1350 . Let's continue there. |
No description provided.