Closed
Description
Those crt2.o and dllcrt2.o files have to match the gcc.exe used. So for example when i use win-gnu target in a msvc toolchain, I'll install my own copy of MINGW, and it should provide gcc.exe and those .o files, and i shouldn't use the rust-provided one.
So I suggest:
- We package these files in "rust-mingw" component instead of current "rust-std" component in win-gnu builds.
- Make people able to use an environment variable or something to specify where to pick these .o files in the linker command.
Metadata
Metadata
Assignees
Labels
Area: linking into static, shared libraries and binariesArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsCategory: This is a bug.Toolchain: GNU, Operating system: WindowsRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.