rust/src/ci/docker/scripts/musl.sh, branch 1.34.2 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.34.2 2018-12-26T04:08:33+00:00 Remove licenses 2018-12-26T04:08:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-12-25T15:56:47+00:00 urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c Update CI-clang to 7.0.0 for Linux dists. 2018-11-14T16:42:06+00:00 Michael Woerister michaelwoerister@posteo 2018-11-14T16:41:54+00:00 urn:sha1:2ec6f340cd29f289fea1c5a672195ceeaf44c475 Update musl to 1.1.20. 2018-09-21T14:03:13+00:00 Adrian Budau adbudau@bitdefender.com 2018-09-21T14:03:13+00:00 urn:sha1:97723db7cf2e19dfd51721d5361c898b52f5a57f Fix typos found by codespell. 2018-08-19T15:41:28+00:00 Matthias Krüger matthias.krueger@famsik.de 2018-08-19T13:30:23+00:00 urn:sha1:71120ef1e5cb885ee45e6148970db6ce93ce1aca Update musl to 1.1.19 and add patch to fix tls issue 2018-07-05T23:17:57+00:00 Marco A L Barbosa malbarbo@gmail.com 2018-07-05T22:53:36+00:00 urn:sha1:f969b61bd61d31b4a6f001b7047fd4a192bedd35 Add --enable-debug flag to musl CI build script 2018-04-10T17:44:47+00:00 Alec Mocatta alecmocatta@users.noreply.github.com 2018-04-10T17:44:47+00:00 urn:sha1:18e95320986243696f31f4b596761eb35759dfe9 Building for x86_64-unknown-linux-musl currently results in an executable lacking debug information for musl libc itself. If you request a backtrace in GDB while control flow is within musl – including sycalls made by musl – the result looks like: #0 0x0000000000434b46 in __cp_end () #1 0x0000000000432dbd in __syscall_cp_c () #2 0x0000000000000000 in ?? () i.e. not very helpful. Adding --enable-debug resolves this, and --enable-optimize re-enables optimisations which default to off given the previous flag. Remove musl/libunwind patch for i686 2018-01-27T22:57:10+00:00 Marco A L Barbosa malbarbo@gmail.com 2018-01-27T22:57:10+00:00 urn:sha1:2875f825fd5a29d94bbfd78b1019ebdedd8d2444 The i686 problem was fixed upstream: https://github.com/llvm-mirror/libunwind/commit/aa805e415f19f50ebc6f5e1e1e4bf9bb7f61816b Build musl with -fPIC for all targets 2018-01-23T23:39:17+00:00 Marco A L Barbosa malbarbo@gmail.com 2018-01-23T23:39:17+00:00 urn:sha1:9b13e403761797127fd19a7c13eeb2429eb1c139 Use libuwind 6.0 for all musl targets 2018-01-23T16:05:31+00:00 Marco A L Barbosa malbarbo@gmail.com 2018-01-23T16:05:31+00:00 urn:sha1:abc1061a656284f6e07008e7fd058a389ab2f33e Do not assume dynamic linking for musl/mips[el] targets 2018-01-22T18:14:51+00:00 Marco A L Barbosa malbarbo@gmail.com 2018-01-12T23:22:06+00:00 urn:sha1:68db72d8cd613f88ea69d37bcd159c4ff659aab1 All musl targets except mips[el] assume static linking by default. This can be confusing https://users.rust-lang.org/t/static-cross-compiled-binaries-arent-really-static/6084 When the musl/mips[el] targets was [added](https://github.com/rust-lang/rust/pull/31298), dynamic linking was chosen because of binary size concerns, and probably also because libunwind [didn't](https://users.rust-lang.org/t/static-cross-compiled-binaries-arent-really-static/6084/8) supported mips. Now that we have `crt-static` target-feature (the user can choose dynamic link for musl targets), and libunwind [6.0](https://github.com/llvm-mirror/libunwind/commits/release_60) add support to mips, we do not need to assume dynamic linking.