Uh oh!
There was an error while loading. Please reload this page.
Require rlibs for dependent crates when linking static executables - #44279
Conversation
rust-highfive
commented
Sep 2, 2017
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
eddyb
commented
Sep 3, 2017
alexcrichton
commented
Sep 5, 2017
@bors: r+ |
bors
commented
Sep 5, 2017
📌 Commit 4950756 has been approved by |
alexcrichton
commented
Sep 7, 2017
@bors: rollup |
Require rlibs for dependent crates when linking static executables This handles the case for `CrateTypeExecutable` and `+crt_static`. I reworked the match block to avoid duplicating the `attempt_static` and error checking code again (this case would have been a copy of the `CrateTypeCdylib`/`CrateTypeStaticlib` case). On `linux-musl` targets where `std` was built with `crt_static = false` in `config.toml`, this change brings the test suite from entirely failing to mostly passing. This change should not affect behavior for other crate types, or for targets which do not respect `+crt_static`.
bors
commented
Sep 8, 2017
☔ The latest upstream changes (presumably #44142) made this pull request unmergeable. Please resolve the merge conflicts. |
4950756 to
6b4bdbdComparecarols10cents
commented
Sep 11, 2017
@bors: r=alexcrichton |
bors
commented
Sep 11, 2017
📌 Commit 6b4bdbd has been approved by |
carols10cents
commented
Sep 11, 2017
@bors: rollup |
Require rlibs for dependent crates when linking static executables This handles the case for `CrateTypeExecutable` and `+crt_static`. I reworked the match block to avoid duplicating the `attempt_static` and error checking code again (this case would have been a copy of the `CrateTypeCdylib`/`CrateTypeStaticlib` case). On `linux-musl` targets where `std` was built with `crt_static = false` in `config.toml`, this change brings the test suite from entirely failing to mostly passing. This change should not affect behavior for other crate types, or for targets which do not respect `+crt_static`.
aidanhs
commented
Sep 13, 2017
It looks like the compile failure is happening in the intended way, but the error message is different because it's being caught earlier. Should I just change the expected error message in the test? Edit: hmm, but the error path and therefore the message will be different based on whether the executable was static. Do I need another special case here? should we make the error messages match? |
alexcrichton
commented
Sep 14, 2017
If possible yeah let's just get the errors to emit through a common path to ensure that they're the same |
6b4bdbd to
841b4a2Comparecarols10cents
commented
Sep 18, 2017
tidy error for you @smaeul! |
smaeul
commented
Sep 18, 2017
How do I fix that without making the error message shorter? |
kennytm
commented
Sep 18, 2017
@smaeul You could remove the spaces around |
This handles the case for `CrateTypeExecutable` and `+crt_static`. I reworked the match block to avoid duplicating the `attempt_static` and error checking code again (this case would have been a copy of the `CrateTypeCdylib`/`CrateTypeStaticlib` case). On `linux-musl` targets where `std` was built with `crt_static = false` in `config.toml`, this change brings the test suite from entirely failing to mostly passing. This change should not affect behavior for other crate types, or for targets which do not respect `+crt_static`.
841b4a2 to
e071e74Comparearielb1
commented
Sep 19, 2017
Test failure: |
e071e74 to
314c2b1Comparecarols10cents
commented
Sep 25, 2017
This looks like it's ready for rereview @alexcrichton ! |
alexcrichton
commented
Sep 25, 2017
@bors: r+ |
bors
commented
Sep 25, 2017
📌 Commit 314c2b1 has been approved by |
bors
commented
Sep 25, 2017
Require rlibs for dependent crates when linking static executables This handles the case for `CrateTypeExecutable` and `+crt_static`. I reworked the match block to avoid duplicating the `attempt_static` and error checking code again (this case would have been a copy of the `CrateTypeCdylib`/`CrateTypeStaticlib` case). On `linux-musl` targets where `std` was built with `crt_static = false` in `config.toml`, this change brings the test suite from entirely failing to mostly passing. This change should not affect behavior for other crate types, or for targets which do not respect `+crt_static`.
bors
commented
Sep 25, 2017
☀️ Test successful - status-appveyor, status-travis |
This handles the case for
CrateTypeExecutableand+crt_static. I reworked the match block to avoid duplicating theattempt_staticand error checking code again (this case would have been a copy of theCrateTypeCdylib/CrateTypeStaticlibcase).On
linux-musltargets wherestdwas built withcrt_static = falseinconfig.toml, this change brings the test suite from entirely failing to mostly passing.This change should not affect behavior for other crate types, or for targets which do not respect
+crt_static.