You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building on Windows, libgcc is dynamically linked by default. In the GCC Linker Options, it says that this is necessary for cross-library exception handling, but for programs that don't need that, this adds an unnecessary dynamic linking to the libgcc DLL, which would have to be distributed with the built executable since it's not available by default on Windows.
Passing -C link-args=-static-libgcc should make libgcc statically linked, but it doesn't seem to override the -shared-libgcc flag. While this suggests a bug or undocumented behavior with the GCC linker, rustc should be aware that the user wants to statically link libgcc and not add the -shared-libgcc linker flag.
I'm using Mingw-builds 4.8.1 on Windows 7 (OS is 64-bit, Mingw is 32-bit) and the Rust 0.11.0 release.
The text was updated successfully, but these errors were encountered:
We used to let gcc add the appropriate version of libgcc to linker command line, so the -static-libgcc switch would work. Later, however, an explicit #[link("gcc_s")] was added in libunwind.rs, which takes precedence.
I suppose this could be reverted, however, if we aspire to invoke 'ld' directly, this wouldn't be a long-term solution. To do this properly, we may have to add some support for conditional linking, similar to --cfg.
…r=Veykril
Increase the buffer size for discover project command
The default value for maxBuffer is 1 MiB[1]. If the discover project command returns stdout or stderr that is greater than 1 MiB, the extension would error with "RangeError: stderr maxBuffer length exceeded".
Set the default value for maxBuffer to 10 MiB for project discovery.
[1] https://nodejs.org/api/child_process.html#child_processexeccommand-options-callback
When building on Windows,
libgcc
is dynamically linked by default. In the GCC Linker Options, it says that this is necessary for cross-library exception handling, but for programs that don't need that, this adds an unnecessary dynamic linking to thelibgcc
DLL, which would have to be distributed with the built executable since it's not available by default on Windows.Passing
-C link-args=-static-libgcc
should makelibgcc
statically linked, but it doesn't seem to override the-shared-libgcc
flag. While this suggests a bug or undocumented behavior with the GCC linker,rustc
should be aware that the user wants to statically linklibgcc
and not add the-shared-libgcc
linker flag.I'm using Mingw-builds 4.8.1 on Windows 7 (OS is 64-bit, Mingw is 32-bit) and the Rust 0.11.0 release.
The text was updated successfully, but these errors were encountered: