Misc #20665: Swig testing of Ruby with MinGW-w64 UCRT

• Status: Closed
• Assignee: -

[[e-mail] (Erez Geva)]

Hi,

I try to add SWIG project testing with already installed Ruby on GitHub Windows2022.

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.yml

The test fails:
https://github.com/erezgeva/swig/actions/runs/10237377988/job/28320593017

Can you advice what is wrong here?

Erez

[[e-mail] (Erez Geva)]

I manage to run Ruby version 3.1.6 with MinGW-w64 UCRT.
I have a crash with 3.2.5, which I will investigate.

This bug can be closed!

Erez

[nobu (Nobuyoshi Nakada)]

• Tracker changed from Bug to Misc
• Backport deleted (3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN)

Maybe https://github.com/ruby/setup-ruby/ helps you?

[alanwu (Alan Wu)]

• Status changed from Open to Closed

[[e-mail] (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.