[Tcl-bugs] [Tk] (oscarfv) tkt (Closed): Don' t use static libgcc when building as shared lib

[<no...@tc...>]

Automated mail by fx, on behalf of no...@tc...

Ticket Change [98591c32155b825473ff018be24c68ed04261c28c6132e898f01774e72d4c46b]
  [Don't use static libgcc when building as shared lib]
  By      oscarfv
  For     Tk
  On      2025-10-27T10:26:14.964
  Details https://core.tcl-lang.org/tk/tinfo?name=98591c32155b825473ff018be24c68ed04261c28c6132e898f01774e72d4c46b
  Ticket  https://core.tcl-lang.org/tk/tktview/71b6efd8f0ac51bf56a5e944f3128a1df9901191

Changed Fields
  closedate: 2025-10-27 10:26:14
  closer:    oscarfv
  icomment:  One big problem with linking statically to libgcc in plugin-based
             applications (such as tcl/tk when using binary packages) is that
             destruction of global objects may break, exchange of C runtime objects
             may also break (due to differences on internal details), exception
             handling may break (there are multiple options in that field: SEH,
             Dwarf and setjmp/longjmp is still around.)

             So, it is quite risky to mix gcc dlls without dynamically linking
             libgcc as well *and* using the same libgcc flavor.

             Contrary to the the _MINGW_ANSI_STDIO issue, this is more of a
             nuisance, as there is no way of removing -static-libgcc without
             patching the tcl/tk build.

             Can we have a configure option to disable -static-libgcc? Would such a
             patch acceptable?
  login:     oscarfv

------------------------------------------------------------
See Tcl/Tk development @ http://core.tcl-lang.org/
------------------------------------------------------------