On Sat, Aug 08, 2026 at 12:24:14AM +0200, Patrice Dumas wrote: > > I remember there was unresolved business with the TEXINFO_XS variable. > > I think that it is resolved. (Except for this new issue I describe > above that popped up recently).
I'll try to replicate the problem. > > As I remember, we were considering making the XS modules mandatory if it > > was detected that they worked at configure-time, in order to reduce the > > number of possible conditions the tests could run under. We were calling > > the value for this "requiredifenabled". > > > > However, for some reasons I did not understand at the time, using this > > setting didn't work: > > > > I propose to remove the reference to TEXINFO_XS=requiredifenabled in > > INSTALL since it does not work as expected for now. Ok? > > > > https://lists.gnu.org/archive/html/bug-texinfo/2026-02/msg00004.html > > > > So I am unsure what the status of the TEXINFO_XS variable is now. > > I do not remember the details, but I remember that I fixed that after > the release. This is fixed now, all the modules depending on the > libraries have a fallback. > [...] > > > Texinfo/XSLoader.pm does not contain the string "requiredifenabled" > > - is that because that behaviour is obtained by default if TEXINFO_XS > > is not set to "omit"? > > This is the reason, yes. OK great, it all makes sense now.
