diff options
| author | bors <bors@rust-lang.org> | 2018-07-10 06:52:20 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-07-10 06:52:20 +0000 |
| commit | 77117e383676176116851d7d3ec04b5e0cf0c456 (patch) | |
| tree | 4de12bf33deac9e05123c404bc830be500039d36 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | b3e7d70ce7730a929fd3d5094e8ad2eb71c3a399 (diff) | |
| parent | 232e77e007eb9ec847f1737cd200102e2c309cf7 (diff) | |
| download | rust-77117e383676176116851d7d3ec04b5e0cf0c456.tar.gz rust-77117e383676176116851d7d3ec04b5e0cf0c456.zip | |
Auto merge of #52177 - ljedrz:bare_gcc_warning, r=alexcrichton
Warn windows-gnu users that the bundled gcc can't compile Add a `DO NOT USE THIS gcc.exe FOR COMPILATION.txt` file to `lib\rustlib\*-pc-windows-gnu\bin` folders in `windows-gnu` installations in order to warn against attempting to use the bundled `gcc.exe` as a C compiler. I'm pretty sure that location is usually found manually, so this should be easily noticeable. This mistake has been made plenty of times and has lead to misunderstandings: Rust: [Bundled gcc (windows x64) is unable to build any c file](https://github.com/rust-lang/rust/issues/24418) gtk-rs: [Compiling on windows](https://github.com/gtk-rs/gtk/issues/625) bzip2-rs: [Build failure at gcc level: blocksort.c not found](https://github.com/alexcrichton/bzip2-rs/issues/30) Alternatives: rename the bundled `gcc.exe` to e.g. `rustc-gcc.exe` or `gcc-linker.exe`. This might require a more comprehensive change or break crates already using it as a linker. r? @alexcrichton
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions