Re: Texinfo 7.2.90 build with mingw.org's MinGW: libtool installation location

Gavin Smith <[email protected]>
Newsgroups gmane.comp.tex.texinfo.bugs
Message-ID <aWywU4DUhESJ2HWY@orangestar>
On Sun, Jan 18, 2026 at 08:33:53AM +0200, Eli Zaretskii wrote:
> > I've read in an email on the libtool mailing list archives that
> > the path $libdir/../bin is used:
> > 
> > Mike Gran wrote:
> > > Because when a MinGW DLL is installed by libtool, the libfoo.lib.a
> > > goes into $libdir and the libfoo.dll goes into $libdir/../bin, which
> > > happens to be $bindir
> > https://lists.gnu.org/archive/html/libtool/2022-11/msg00000.html
> > 
> > So e.g.  /usr/lib/texi2any becomes /usr/lib/texi2any/../bin = /usr/lib/bin.
> > 
> > If this is right, then one workaround is to use an extra layer of directories.
> > 
> > If xsdir is instead /usr/lib/texi2any/lib, then this would lead to the
> > directory /usr/lib/texi2any/bin being used instead, which is not so bad.
> 
> Right, but these directories are unlikely to be on PATH.  $prefix/bin
> is usually on PATH, so if, as Patrice says, SWIG needs to load the
> libtexinfo*.dll DLLs without reading the *.la files, it is better to
> install them in $prefix/bin.

SWIG is not a necessary part of Texinfo.  We keep on tripping over these
non-essential features.  The modules are loaded in Texinfo::XSLoader by
DynaLoader, a Perl module, not by SWIG.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.