Error building nix 0.6.0 on FreeBSD 10.3 (latest Rust nightly)

[alexreg]

error[E0432]: unresolved import `libc::SIGPWR`
  --> /home/alexuk/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.6.0/src/sys/signal.rs:49:5
   |
49 |     SIGPWR,
   |     ^^^^^^ no `SIGPWR` in `libc`

error[E0432]: unresolved import `libc::SIGSTKFLT`
  --> /home/alexuk/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.6.0/src/sys/signal.rs:50:5
   |
50 |     SIGSTKFLT,
   |     ^^^^^^^^^ no `SIGSTKFLT` in `libc`. Did you mean to use `SIGSTKSZ`?

error[E0432]: unresolved import `libc::SIGPOLL`
  --> /home/alexuk/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.6.0/src/sys/signal.rs:52:5
   |
52 |     SIGPOLL, // Alias for SIGIO
   |     ^^^^^^^ no `SIGPOLL` in `libc`. Did you mean to use `SIGILL`?

error[E0432]: unresolved import `libc::SIGUNUSED`
  --> /home/alexuk/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.6.0/src/sys/signal.rs:53:5
   |
53 |     SIGUNUSED, // Alias for 31
   |     ^^^^^^^^^ no `SIGUNUSED` in `libc`

error[E0308]: mismatched types
   --> /home/alexuk/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.6.0/src/unistd.rs:188:47
    |
188 |     let res = unsafe { libc::sethostname(ptr, len) };
    |                                               ^^^ expected i32, found usize

error: aborting due to previous error

[posborne]

Hi @alexreg, can you verify that this occurs on the latest from git as well. Also, is this failure only with nightly?

[alexreg]

Actually, I've just verified it only occurs with nix 0.6 (and maybe earlier). Fixed from 0.7 onwards. So perhaps making a new 0.6 release and yanking the old one is the right way to go. :)

…

Sent from my iPhone

On 10 Feb 2017, at 04:45, Paul Osborne ***@***.***> wrote: Hi @alexreg, can you verify that this occurs on the latest from git as well. Also, is this failure only with nightly? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[kamalmarhubi]

@alexreg does this error come up on stable Rust? Trying to narrow down the variables a bit.

Also, this raises an interesting question: how far back do we want to support.

[alexreg]

Yep, happens on stable Rust too. The fix should be relatively straightforward in this case, although the code has been restructured quite significantly, it seems.

…

On 14 Feb 2017, at 06:03, Kamal Marhubi ***@***.***> wrote: @alexreg <https://github.com/alexreg> does this error come up on stable Rust? Trying to narrow down the variables a bit. Also, this raises an interesting question: how far back do we want to support. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#507 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF3D9_BZhp3_esH4U57md915tTXrORks5rcUO9gaJpZM4L7neN>.

[Susurrus]

@alexreg You also opened #567, which makes me think this issue is outdated. If so, please close this.

[alexreg]

Well, this one seemed to be solved (I think?), but some new similar errors appeared.