Should this project be referring to ruby 3.4.1?

[chadlwilson]

I understand from ruby/ruby@48d4efc#diff-741f0195763b008706a42eea7b8c9a1f1c975ea578ccf2b0433ff9f45ddc266eL14 that 3.4.1 fixed the RUBY_PATCHLEVEL to imply a non-dev version of Ruby.

I am certainly very far from being an expert here, but it seems that this might be relevant given the var appears to distinguish between dev and non-dev versions of Ruby and appears to impact whether ruby_abi_version is required/available in extensions in some cases? It goes a bit over my head, but referred to in grpc) and there's logic based on this within ruby itself if it is a negative value (dev version).

$ mise x ruby@3.4.0 -- ruby -e "puts RUBY_PATCHLEVEL"
-1
$ mise x ruby@3.4.1 -- ruby -e "puts RUBY_PATCHLEVEL"
0

Apologies for the question from possible ignorance - possibly irrelevant given using an older bootstrap ruby. 🙏 Feel free to ignore or school me.

(related indirectly to #135)

[flavorjones]

@chadlwilson Thanks for asking this question. Yes, I want to update this version of Ruby, and will do so sooner or later. But I'm unaware of anything that's broken using 3.4.0. Is there something broken for you?

[chadlwilson]

Something is broken, but I don't know right now if it has anything to do with rake-compiler or rake-compiler-dock - or is more to do with the install-time ruby version or build/test infra.

To be fair, I'm fishing a bit here to see if someone with deeper knowledge might see that diff and say "yes, I can see how that could be an issue when cross compiling" (perhaps similar to the issues you had to wait for 3.3.5 to fix!). But I don't know that to be true, so if nothing stands out - probably best to ignore me 😅

Was trying to help out with moving along grpc gems precompiled for 3.4, and having an issue with the "officially built" gems at install time due toa missing ruby_abi_version symbol preventing loading (grpc has custom symbol stripping logic for its extensions). Replicating the test/build environment is painful as it seems to rely on google-only docker images and limited ability for community folks to easily get access to build artifacts - so I'll probably have to set it all up locally inside a Linux VM or wait for someone more competent to weigh in from Google/grpc 😅

[flavorjones]

Ah, interesting. Yes, ruby_abi_version is something that might be affected by the "development version" of Ruby being used in the container. Can you point me at the grpc issue, please.

[flavorjones]

I'll find some time to ship a version of rake-compiler-dock with ruby bumped to 3.4.1, but may not get to it today.

Edit: see #142

[chadlwilson]

It's the PR I raised to do the various janitorial hijinx needed for new extension compiles - currently stuck at grpc/grpc#38338 (comment) - although the Googlers who know the history and grpc specifics about the symbol stripping and how Ruby ABI checking is intended to work probably haven't had a chance to look at it yet.

[flavorjones]

See https://github.com/rake-compiler/rake-compiler-dock/releases/tag/v1.7.1

[chadlwilson]

Thanks! I assume it is necessary for users to change RUBY_CC_VERSION, similar to https://github.com/rake-compiler/rake-compiler-dock/releases/tag/v1.6.0 ?

[flavorjones]

I assume it is necessary for users to change RUBY_CC_VERSION

Yes.

[chadlwilson]

Thanks again for your responsiveness, you're a star! 🫡

Hopefully this nails it for grpc at least.