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 RUBY_CC_VERSION has some ruby version that are not available as cross compile platforms, they are simply ignored for building the gem. In this case it just shows the warning no configuration section for specified version of Ruby (rbconfig-x64-mingw32-2.3.3) or similar. However it turned out, that the versions defined in RUBY_CC_VERSION are still respected in the required_ruby_version of the resulting gemspec, although no such binaries have been built.
The issue happens practically in rake-compiler-dock which has added the new platform "x64-mingw-ucrt" which supports only ruby-3.1. On the other hand the "x64-mingw32" doesn't support ruby-3.1, but only ruby-2.4 to 3.0. This is in accordance to the change of RubyInstaller-3.1. RUBY_CC_VERSION is set to 3.1.0:3.0.0:2.7.0:2.6.0:2.5.0:2.4.0in any case. The resulting gems should reflect the version range of the given platform, but both platform gemspecs actually state ruby-2.4 to 3.1 compatibility, currently.
The text was updated successfully, but these errors were encountered:
larskanis
added a commit
to larskanis/rake-compiler
that referenced
this issue
Jan 12, 2022
This was raised by @flavorjones in sparklemotion/nokogiri#2409 (comment) .
When
RUBY_CC_VERSION
has some ruby version that are not available as cross compile platforms, they are simply ignored for building the gem. In this case it just shows the warningno configuration section for specified version of Ruby (rbconfig-x64-mingw32-2.3.3)
or similar. However it turned out, that the versions defined inRUBY_CC_VERSION
are still respected in therequired_ruby_version
of the resulting gemspec, although no such binaries have been built.The issue happens practically in rake-compiler-dock which has added the new platform "x64-mingw-ucrt" which supports only ruby-3.1. On the other hand the "x64-mingw32" doesn't support ruby-3.1, but only ruby-2.4 to 3.0. This is in accordance to the change of RubyInstaller-3.1.
RUBY_CC_VERSION
is set to3.1.0:3.0.0:2.7.0:2.6.0:2.5.0:2.4.0
in any case. The resulting gems should reflect the version range of the given platform, but both platform gemspecs actually state ruby-2.4 to 3.1 compatibility, currently.The text was updated successfully, but these errors were encountered: