about summary refs log tree commit diff
path: root/src/test/run-pass/thinlto
diff options
context:
space:
mode:
authorJonathan Turner <jonathandturner@users.noreply.github.com>2016-10-06 08:35:43 -0700
committerGitHub <noreply@github.com>2016-10-06 08:35:43 -0700
commit9ceef4e004a521821d227cf6cfd4726b44e4ac8d (patch)
tree6af2da9c8f19a24c7c0ff47e5b5abd34d4bcffd1 /src/test/run-pass/thinlto
parenta19e22e2e98134d90fe59e7927d7d9f5a6c00d07 (diff)
parent7937f6ccdea38fd76a9ef98b41742d9318e25e4b (diff)
downloadrust-9ceef4e004a521821d227cf6cfd4726b44e4ac8d.tar.gz
rust-9ceef4e004a521821d227cf6cfd4726b44e4ac8d.zip
Rollup merge of #36972 - nastevens:fix-rustbuild-per-target-musl-root, r=alexcrichton
Fix rustbuild per-target musl root

In #36292, support was added to target musl libc for ARM targets using rustbuild. Specifically, that change allowed the addition of per-target `musl-root` options in the rustbuild `config.toml` so that multiple targets depending on musl could be built. However, that implementation contained a couple of omissions: the `musl-root` option was added to the config, but was never added to the TOML parsing, and therefore was not actually being loaded from `config.toml`. This PR rectifies that.

Using these changes and a heavily modified version of the buildbot Docker container, I have been able to build rust targeting `armv7-unknown-linux-musleabihf` and have successfully run the binaries on a Raspberry Pi 3. I'm also planning to test `arm-unknown-linux-musleabi` and `arm-unknown-linux-musleabihf` systems, but have no reason to believe that this change would not simply work on those targets.
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions