libc: CI segfaults on FreeBSD

CI has started to segfault on FreeBSD since the latest nightly.

This build passed with nightly-x86_64-unknown-freebsd 1.39.0 (760226733 2019-08-22) This build failed with nightly-x86_64-unknown-freebsd 1.39.0 (9eae1fc0e 2019-08-23)

The segfault is triggered by the build.rs of rand_pcg v0.1.2 and rand_chacha v0.1.1 (cc @dhardy), which AFAICT only call autocfg (cc @cuviper ). There was an update of autocfg recently so initially I thought that might be it, but it seems that the builds were working correctly with that update, so AFAICT neither autocfg nor rand are at fault here (cc @mati865 @asomers ). Looking at the recently merged PRs in rust-lang/rust, I don’t see any suspicious one.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 27 (27 by maintainers)

Commits related to this issue

Most upvoted comments

maybe bumping libc in rust-lang/rust to 0.2.62 fixes this issue.

Updating getrandom in https://github.com/rust-lang/rust/pull/63806 pulled libc = 0.2.62 so the answer should come soon.

@cuviper if libstd is using 0.2.61 then that might explain this. IIRC, the build.rs being used there had a bug for freebsd and wasn’t passing --cfg freebsd11 by default. That was fixed in 0.2.62, so maybe bumping libc in rust-lang/rust to 0.2.62 fixes this issue.