Issue #20665 has been updated by ErezGeva2@gmail.com (Erez Geva). The problem was I add `-static-libstdc++ -static-libgcc` and `-lucrt` to the linking. But once I removed and left only -l<Ruby lib> <RbConfig::CONFIG["LIBS"]> in linking. All my tests passed smoothly. Sometime Windows require some hacking. And sometime it just get in the way. ---------------------------------------- Misc #20665: Swig testing of Ruby with MinGW-w64 UCRT https://bugs.ruby-lang.org/issues/20665#change-109367 * Author: ErezGeva2@gmail.com (Erez Geva) * Status: Closed ---------------------------------------- Hi, I try to add SWIG project testing with already installed Ruby on [GitHub Windows2022](https://github.com/actions/runner-images/blob/main/images/windows/Windows202...). I manage to test with Ruby version 3.0.7 and installed mingw-w64-x86_64-ruby version 3.1.5. Both are build with MinGW-w64. See: https://github.com/swig/swig/pull/2981 Now I want to use the more newer Ruby. GitHub Windows2022 provides 2 Ruby version 3.1.6 and 3.2.5 which are build with MinGW-w64 UCRT. I try and use mingw-w64-ucrt-x86_64-gcc with more mingw-w64-ucrt-x86_64-XXX packages. My testing can be found here: https://github.com/erezgeva/swig/blob/win_ruby2/.github/workflows/windows.ym... The test fails: https://github.com/erezgeva/swig/actions/runs/10237377988/job/28320593017 Can you advice what is wrong here? Erez -- https://bugs.ruby-lang.org/