> From: Gavin Smith <[email protected]> > Date: Sun, 18 Jan 2026 10:38:48 +0000 > Cc: [email protected], [email protected] > > > > Is this a new problem? > > > > Yes. > > > > > Were the libraries installed in the wrong place with Texinfo 7.2? > > > > No, they were installed together with the XS DLLs. But Texinfo 7.2 > > didn't use libtool for that, did it? > > It did. We've always used libtool for the XS modules. I don't know > what would have changed. We moved from libtool 2.5.3 to libtool 2.5.4 > but the use of "../bin" for library locations is much older than that.
Then I don't know what changed. > You haven't reported whether texi2any can find these installed libraries > in "d:/usr/lib/bin". You could check this by setting the TEXINFO_XS > environment variable to "debug" when running installed Texinfo. I didn't yet install Texinfo 7.2.90 in a way that I can use it. I just ran "make install prefix=..." to see what the installation procedure does, but I used a temporary directory for prefix. However, if these libraries are all loaded via XSLoader.pm, I see no reason why it could fail to find them. The problems I had in mind are only relevant to when a DLL is loaded without its leading directories, which then causes Windows to look for it in the places I described. I understand now that this should basically never happen, so I guess I just confused you guys for no good reason, sorry.
