This is just a heads-up that the Nokogumbo gem as of version 1.4.7 (current version in the Portage tree: 1.4.6) has removed a workaround for Gentoo. If the current ebuild fails to build version 1.4.7 of the gem, take a look at the following commit and create a patch to add the workaround to the ebuild. https://github.com/rubys/nokogumbo/commit/ef0497d2be380b7b83836329d08889e4d4efb940 (I can't test it myself because I don't install Rubies with Portage.) Reproducible: Didn't try
Thanks for the heads up. It would be helpful to have had some explanation of the actual issues or reasoning in the commit messages (both the one adding the workaround and the one removing it). But I think I now understand what is going on. Our ruby is compiled with the --no-undefined linker flag by default, and I think that is why this was added in the first place. I've now added "sed -i -e 's:-Wl,--no-undefined::' ext/nokogumboc/Makefile" to our nokogumbo 1.4.7 ebuild, like we do elsewhere were similar linking is needed.
