>> That could work yes. Something akin to: >> "This ruby version wasn't tested, blah blah". > > OK, can you send a patch for that?
I will once I have something working on 3.0. >> I'm trying to figure out why the symbol isn't exported, >> I might come back with another patch. But just in case >> you might have an idea what's going on. > > I haven't built+tested ruby.git in ages (my computers are too slow). > It could be a failure to completely clean out the old 2.8 stuff > (either in the Ruby worktree, install paths, or unicorn worktree). I don't think so, I'm building from a fresh docker image + fresh unicorn clone. I also tested other similar gems (e.g. puma) and they export the functions just fine. I have to admit that I don't understand enough about the build process to figure out what's going on, so I'm not very confident I'll find a fix.
