Fixes #30521 and #30627 by adding new snapshots

[dhuseby]

@alexcrichton please upload the following snapshots when landing this patch:

• https://github.com/dhuseby/rust-manual-snapshots/raw/master/rust-stage0-2015-12-18-3391630-bitrig-x86_64-6476e1562df02389b55553b4c88b1f4fd121cd40.tar.bz2
• https://github.com/dhuseby/rust-manual-snapshots/raw/master/rust-stage0-2015-12-18-3391630-freebsd-i386-7e624c50494402e1feb14c743d659fbd71b448f5.tar.bz2
• https://github.com/dhuseby/rust-manual-snapshots/raw/master/rust-stage0-2015-12-18-3391630-freebsd-x86_64-91724d4e655807a2a2e940ac50992ebeaac16ea9.tar.bz2

I'm still working on dragonfly bsd. it needs some maintenance love.

thanks!

[rust-highfive]

r? @nikomatsakis

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

[dhuseby]

Fixes #30627 too.

[sfackler]

Was this intentionally merged into master?

[mneumann]

@dhuseby I build the 2015-12-18 snapshot for DragonFly:

http://www.ntecs.de/downloads/rust/rust-stage0-2015-12-18-3391630-dragonfly-x86_64-e74d79488e88ac2de3bd03afd5959d2ae6e2b628.tar.bz2

You only need to patch the SIGSTACKSZ thing, then it builds fine, IIRC.

I also have pushed some patches to https://github.com/rust-lang-nursery/libc, which should help with building more recent versions of Rust (it is broken on libc).

[mneumann]

@dhuseby : If you need help with setting up continuous builds for DragonFly, please let me know.

[dhuseby]

@mneumann i will for sure. so far it seems to be going well.

[mneumann]

@dhuseby : cool! Also feel free to submit a patch to etc/snapshots.txt for DragonFly :)

[dhuseby]

@mneumann I will add the dragonfly snapshot as soon as I can figure out how to get it to build at the last snap rev.

[mneumann]

@dhuseby : Ok, IIRC I had to patch SIGSTACKSZ constant in rust's libc. I just had to unfold it manually to it's value.

[pnkfelix]

Did anyone answer @sfackler 's question above? Was there a reason this was directly pushed to master rather than going through bors? (And I don't see any r+'s... ?)

[pnkfelix]

(having said that, the change seems pretty innocent...)

[dhuseby]

@pnkfelix it's because i'm dumb sometimes and i clicked the "merge" button here in github.

[dhuseby]

@pnkfelix what's the correct way to merge a PR into bors?

[sfackler]

"@bors r+"

[dhuseby]

@sfackler thanks!

[alexcrichton]

Thanks for the snapshots @dhuseby and @mneumann! It looks like @dhuseby's snapshots have been uploaded (by @brson I guess?), but @mneumann it looks like the DragonFly snapshot is still missing and your link unfortunately has a host name that doesn't resolve for me. (in the future as well, could you guys also paste the sha256 with the links as well?)

And yeah @dhuseby just be careful not to merge manually, but no worries!

[mneumann]

@alexcrichton : I pushed the snapshot to @dhuseby 's repo. Then we both opened a pull requests probably at the same time. Next time sha256 👍

[alexcrichton]

@mneumann cool, thanks! I've uploaded that snapshot now