Fix size of time_t in vxworks

[hax0kartik]

Description

This fixes the size of time_t in VxWorks which was incorrectly set to c_long. This broke compatibility with 32-bit targets.

Requesting stable-nomination.

Sources

VxWorks sources are copyrighted.

Checklist

• Relevant tests in libc-test/semver have been updated
• No placeholder or unstable values like *LAST or *MAX are
  included (see #3131)
• Checked locally on VxWorks.

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @tgross35 (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[hax0kartik]

@rustbot label stable-nominated

[tgross35]

Cc @jackorobot @biabbas would you be able to double check this?

I know there were some surprising differences on vxworks, from #4043.

[biabbas]

@tgross35
Yes, this is correct. To avoid the problems like year 2038 problem, the default size of time_t on 32 bits VxWorks targets is 64 bits.

[tgross35]

Thanks for confirming. Looks like this has existed since #1408 (cc @BaoshanPang)