On Sat, Jan 17, 2026 at 07:33:42PM +0000, Gavin Smith wrote: > On Sat, Jan 17, 2026 at 08:08:11PM +0100, [email protected] wrote: > > On Sat, Jan 17, 2026 at 06:42:53PM +0000, Gavin Smith wrote: > > > > I just commited changes to avoid loading XS overrides when XS modules > > > > are disabled at configure time. I believe that the issue you reported > > > > was there for a long time, maybe even since the first MiscXS modules. > > > > It never showed in practice because the situation do not often arises, > > > > and maybe we just did make clean when it happened, and because before > > > > some point, with the C codes in libraries, the modules could be loaded > > > > and used even if XS modules were disabled, and it would not have been > > > > noticed unless one had TEXINFO_XS=debug set. > > > > > > I thought it was disabled in Texinfo::XSLoader. texi2any.pl sets > > > $Texinfo::XSLoader::disable_XS if XS modules are disabled. However, > > > the tests under tta/perl/t don't use texi2any.pl. > > > > For t/z_misc/*.t tests, I plan to add the same BEGIN block that I just > > added to t/test_utils.pl. Should I proceed or do you have a better > > idea? > > The only other idea I have is that Texinfo::XSLoader could get the value > itself in its own BEGIN { } block.
Indeed, I did not realize that XSLoader depended on Texinfo::ModulePath. If we do that we should probably remove the corresponding BEGIN blocks from texi2any and test_utils.pl, as they become useless. That's probably the best to do. -- Pat
