diff options
| author | bors <bors@rust-lang.org> | 2015-02-07 12:01:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-02-07 12:01:31 +0000 |
| commit | 80627cd3cc4099b76cb2fb26ebe2f2f8a6c2335e (patch) | |
| tree | b6062b374e3ccd87b56e92436df74c3b0d960e6d /src/libstd/sys/unix/stack_overflow.rs | |
| parent | a08504bb35f5cb36b702750ba105063d1e2972ff (diff) | |
| parent | 48b6aef6605794a9da0d9254960a91bbea0a0737 (diff) | |
| download | rust-80627cd3cc4099b76cb2fb26ebe2f2f8a6c2335e.tar.gz rust-80627cd3cc4099b76cb2fb26ebe2f2f8a6c2335e.zip | |
Auto merge of #22023 - alexcrichton:oops-picked-the-wrong-plugin, r=nikomatsakis
The compiler would previously fall back to using `-L` and normal lookup paths if a `--extern` path was specified but it did not match (wrong architecture, for example). This commit removes this behavior and forces the hand of the crate loader to *always* use the `--extern` path if specified, no matter whether it is correct or not. This fixes a bug today where the compiler's own libraries are favored in cross compilation by accident. For example when a crate using the crates.io version of `log` was cross compiled, Cargo would compile `log` for the target architecture. When loading the macros, however, the compiler currently favors using the *host* architecture (for plugins), and because the `--extern log=...` pointed at an rlib for the target architecture, that lookup failed. The crate loader then fell back on `-L` paths to find the compiler-used `log` crate (the wrong one!) and then a compile failure happened because the logging macros are slightly different.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
