Add settimeofday for solaris/illumos

[GrayJack]

Closes #1547

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gnzlbg (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[gnzlbg]

@mati865 all musl targets are broken on nightly, is this known ?

[gnzlbg]

So the PR that broke this has been reverted and the next nightly shouldn't have this issue.

[mati865]

Yeah all targets packaging start objects are broken.
Revert PR has failed multiple times (very unlucky) rust-lang/rust#65342 so it will be fixed tomorrow.

[GrayJack]

Is it fixed now?

[gnzlbg]

@GrayJack thanks for the ping, yes, it was fixed a couple of hours ago.

@bors: r+

[bors]

📌 Commit fb06358 has been approved by gnzlbg

[bors]

⌛ Testing commit fb06358 with merge 99bef8d...

[bors]

💔 Test failed - checks-cirrus-freebsd-11

[gnzlbg]

cc @asomers @kinnison - so apparently rustup fails on FreeBSD11 because of some components not being available.

EDIT: @kinnison this looks like a rustup bug, where it tries to install components that are not available for a target. Can it be that the new profiles do not know that certain targets never have some components ? (I'm not sure if FreeBSD11 sometimes has clippy and rustfmt).

[mati865]

^ opened #1550

[kinnison]

EDIT: @kinnison this looks like a rustup bug, where it tries to install components that are not available for a target. Can it be that the new profiles do not know that certain targets never have some components ? (I'm not sure if FreeBSD11 sometimes has clippy and rustfmt).

I'm aware of something like this on lower tier platforms yes. I've a fix in-train which might go out tomorrow for that part.

[asomers]

cc @asomers @kinnison - so apparently rustup fails on FreeBSD11 because of some components not being available.

EDIT: @kinnison this looks like a rustup bug, where it tries to install components that are not available for a target. Can it be that the new profiles do not know that certain targets never have some components ? (I'm not sure if FreeBSD11 sometimes has clippy and rustfmt).

FreeBSD11 is supposed to have clippy and rustfmt, as should most platforms. But it hasn't since late May due to this bug: rust-lang/rust#62558 .

[gnzlbg]

@bors: r+

[bors]

💡 This pull request was already approved, no need to approve it again.

• This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.
• There's another pull request that is currently being tested, blocking this pull request: Support vxWorks in libc-test #1543

[bors]

📌 Commit fb06358 has been approved by gnzlbg

[bors]

⌛ Testing commit fb06358 with merge d44c427...

[bors]

💔 Test failed - status-azure

[GrayJack]

Doesn't seem to have something to do with my changes, only linux-android failed

[gnzlbg]

@bors: retry

[bors]

⌛ Testing commit fb06358 with merge bf877ba...

[bors]

☀️ Test successful - checks-cirrus-freebsd-10, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, status-azure
Approved by: gnzlbg
Pushing bf877ba to master...