Skip to content

NetBSD: correct link_name of some time-related functions #1063

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

Merged
merged 1 commit into from
Aug 16, 2018

Conversation

jakllsch
Copy link
Contributor

The futimes(), lutimes(), mq_timedreceive(), and mq_timedsend()
functions were linking against legacy library symbols that need 32-bit
time_t in structures, resulting in an ABI mismatch with 64-bit time_t.

The futimes(), lutimes(), mq_timedreceive(), and mq_timedsend()
functions were linking against legacy library symbols that need 32-bit
time_t in structures, resulting in an ABI mismatch with 64-bit time_t.
@rust-highfive
Copy link

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@gnzlbg
Copy link
Contributor

gnzlbg commented Aug 15, 2018

@alexcrichton I've been getting this sparc64 failure for a while now, so often, that it is not spurious I think, and just came to libc to see if it was happening here too. rust-lang/rust probably will get this as well, so it might be worth opening an issue, pinging @malbarbo and trying to find a different image or upload a backup somewhere else that we can update the buildbots to.

@malbarbo
Copy link
Contributor

Its seems that the site is in maintenance mode. See https://lists.debian.org/debian-infrastructure-announce/2018/08/msg00001.html

@alexcrichton
Copy link
Member

Thanks @jakllsch!

I'll work on CI in a bit

@alexcrichton alexcrichton merged commit b6dacea into rust-lang:master Aug 16, 2018
@jakllsch jakllsch deleted the netbsd-time50-fixes branch August 16, 2018 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants