On Sat, Jan 17, 2026 at 08:41:08PM +0100, [email protected] wrote: > On Sat, Jan 17, 2026 at 07:33:42PM +0000, Gavin Smith wrote: > > 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.
Just found out that this is still not right. Now that Texinfo::ModulePath enable_xs value is used, it becomes problematic for CheckXS. Indeed, the value in Texinfo::ModulePath is set by the Makefile based on configure results. CheckXS, when it loads Texinfo::XSLoader gets the current Texinfo::ModulePath enable_xs value that corresponds with the value set by the previous run of configure + make. I will unset disable_XS forcibly in TestXS.pm before calling Texinfo::XSLoader::init. -- Pat
