-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warn windows-gnu users that the bundled gcc can't compile #52177
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Thanks! I wonder though if perhaps we could start out with a |
I've thought about it, but it might not be visible enough - when someone finds |
Ok! Although perhaps a dash in the middle as I'm not sure I trust out shell scripts to handle spaces in filenames :( |
@bors: r+ |
📌 Commit 232e77e has been approved by |
…hton 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](rust-lang#24418) gtk-rs: [Compiling on windows](gtk-rs/gtk#625) bzip2-rs: [Build failure at gcc level: blocksort.c not found](trifectatechfoundation/bzip2-rs#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
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](#24418) gtk-rs: [Compiling on windows](gtk-rs/gtk#625) bzip2-rs: [Build failure at gcc level: blocksort.c not found](trifectatechfoundation/bzip2-rs#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
☀️ Test successful - status-appveyor, status-travis |
Add a
DO NOT USE THIS gcc.exe FOR COMPILATION.txt
file tolib\rustlib\*-pc-windows-gnu\bin
folders inwindows-gnu
installations in order to warn against attempting to use the bundledgcc.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
gtk-rs: Compiling on windows
bzip2-rs: Build failure at gcc level: blocksort.c not found
Alternatives: rename the bundled
gcc.exe
to e.g.rustc-gcc.exe
orgcc-linker.exe
. This might require a more comprehensive change or break crates already using it as a linker.r? @alexcrichton