-
Notifications
You must be signed in to change notification settings - Fork 60
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
Build failure at gcc level: blocksort.c not found #30
Comments
Thanks for the report! It looks like |
GCC is there, it's the one bundled with |
The gcc we ship that's bundled isn't able to compile C files, though, so you'll want to install a local gcc toolchain elsewehre |
You're right - I once read somewhere (not an official source as far as I remember) that this GCC was supposed to work like the real deal, but I guess that person was wrong. I used the one from my Thanks! Case closed |
I've tried to find that piece of information in order to comment on it, but instead I found lots of other cases where people were surprised that the bundled |
Seems plausible to me! |
…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](alexcrichton/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](alexcrichton/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
bzip2-sys
seems to refuse to build due to missingblocksort.c
(it is indeed not present in the relatedbuild
directory).I'm using
rustc 1.28.0-nightly-gnu-x64
with Win 7.The text was updated successfully, but these errors were encountered: