<commit_before>Unofficial rust and cargo binaries for the `arm-unknown-linux-gnueabihf`
triple.

Since the `arm-unknown-linux-gnueabihf` triple is not officially supported by
the Rust project, there are no official build bots that enforce the "Never
Break the Build" policy. This means that the nightly builds may break from time
to time, and also that bugs may be unintentionally introduced (or fixed!) in
every PR without the knowledge of the author/reviewers.

However, I do run the full cargo and rust test suite with each nightly, and
unconditionally upload the nightly even if some tests fail (otherwise this
folder would be empty :P). Each uploaded nightly is accompanied by a text file
that contains the whole test suite output, this gives you an idea of what
doesn't work. (Last time I checked 99% of the crate unit tests passed though).

# Tested devices

Not comprehensive and likely outdated list of devices that have passed some
form of smoke test.

Note: The format is $DEVICE + $DATE @ $DATE_OF_LAST_SMOKE_TEST

- Odroid XU (ARMv7 SBC) + Raspbian @ today(this is the cargo build bot)
- Odroid XU (ARMv7 SBC) + Wheezy @ today (this is the rust build bot)
- Odroid XU (ARMv7 SBC) + Arch @ 2015-05-30
- Beaglebone (ARMv7 SBC) + Arch @ 2015-05-30
- Raspberry Pi (ARMv6 SBC) + Raspbian @ 2015-02-04
- Samsung Chromebook 2 (ARMv7 Laptop) + Gentoo @ 2015-02-06

# Installation

I recommend using multirust:

https://github.com/brson/multirust

$ curl -sf https://raw.githubusercontent.com/brson/multirust/master/blastoff.sh | sh

$ cd /path/to/empty/folder

$ wget $CARGO_TARBALL

$ wget $RUST_TARBALL<commit_msg>fix 0-README<commit_after>Unofficial rust and cargo binaries for the `arm-unknown-linux-gnueabihf`
triple.

Since the `arm-unknown-linux-gnueabihf` triple is not officially supported by
the Rust project, there are no official build bots that enforce the "Never
Break the Build" policy. This means that the nightly builds may break from time
to time, and also that bugs may be unintentionally introduced (or fixed!) in
every PR without the knowledge of the author/reviewers.

However, I do run the full cargo and rust test suite with each nightly, and
unconditionally upload the nightly even if some tests fail (otherwise this
folder would be empty :P). Each uploaded nightly is accompanied by a text file
that contains the whole test suite output, this gives you an idea of what
doesn't work. (Last time I checked 99% of the crate unit tests passed though).

# Tested devices

Not comprehensive and likely outdated list of devices that have passed some
form of smoke test.

Note: The format is $DEVICE + $DISTRO @ $DATE_OF_LAST_SMOKE_TEST

- Odroid XU (ARMv7 SBC) + Raspbian @ today (this is the cargo build bot)
- Odroid XU (ARMv7 SBC) + Wheezy @ today (this is the rust build bot)
- Odroid XU (ARMv7 SBC) + Arch @ 2015-05-30
- Beaglebone (ARMv7 SBC) + Arch @ 2015-05-30
- Raspberry Pi (ARMv6 SBC) + Raspbian @ 2015-02-04
- Samsung Chromebook 2 (ARMv7 Laptop) + Gentoo @ 2015-02-06

# Installation

I recommend using multirust:

https://github.com/brson/multirust

$ curl -sf https://raw.githubusercontent.com/brson/multirust/master/blastoff.sh | sh

$ cd /path/to/empty/folder

$ wget $CARGO_TARBALL

$ wget $RUST_TARBALL
{'fraction_non_alphanumeric': 0.07244143033292232, 'fraction_numerical': 0.025585696670776818, 'mean_word_length': 4.233870967741935, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1240721', 'n_tokens_mistral': 1090, 'n_tokens_neox': 1011, 'n_words': 445}