-
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
Should rustc.exe be statically linked to libgcc etc.? #1603
Comments
We need to do something here for sure. I'm not sure where the libgcc dependency is, and if we need it for every rust crate or just rustc. Possibly worse than that is that rustc has a run-time dependency on gcc.exe. |
I do not think this is fixable in the timeframe in question. We're still very much wedded to mingw on windows. |
Possibly we should ship libgcc and when rustc runs, it can discover the missing gcc/ld it will need to link stuff and fail gracefully with an error message rather than just reporting a missing DLL at startup. |
Not critical for 0.6; de-milestoning |
Nominating for milestone 5, production-ready |
sub-bug / dupe of #3459, mingw has to be generally removed from dependencies |
They currently also point to filenames, which is redundant. current - [ ] thir.md - [ ] line 7: 2022-04 - [ ] line 60: 2022-08 - [ ] traits/chalk.md - [ ] line 4: 2022-05 proposed - thir.md - [ ] line 7: 2022-04 - [ ] line 60: 2022-08 - traits/chalk.md - [ ] line 4: 2022-05
They currently also point to filenames, which is redundant. current - [ ] thir.md - [ ] line 7: 2022-04 - [ ] line 60: 2022-08 - [ ] traits/chalk.md - [ ] line 4: 2022-05 proposed - thir.md - [ ] line 7: 2022-04 - [ ] line 60: 2022-08 - traits/chalk.md - [ ] line 4: 2022-05
Right now a user would have to have MinGW installed, and its bin directory on their path, in order to run rustc. Perhaps those dependencies should either be taken care of by the installer, or be statically linked into the executable?
The text was updated successfully, but these errors were encountered: