Jean Boussier <[email protected]> wrote: > >> 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.
Do the current dependencies (kgio, raindrops) export alright, as well? Might be worth comparing the generated Makefile with other gems and see if there's missing flags or such. > 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. I'm not a build/linker expert, either. Also, did things work a few days/weeks ago when ruby.git was still 2.8? Maybe mkmf.log has clues, somewhere, too... *shrug* my brain hurts from other stuff -- unsubscribe: one-click, see List-Unsubscribe header archive: https://yhbt.net/unicorn-public/
