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.

    • ... Gavin Smith
  • Re: ... pertusus
    • ... Gavin Smith
      • ... Eli Zaretskii
      • ... pertusus
      • ... Eli Zaretskii
      • ... pertusus
      • ... Gavin Smith
      • ... Gavin Smith
      • ... Eli Zaretskii
      • ... Gavin Smith
      • ... Eli Zaretskii
      • ... pertusus
      • ... Bruno Haible via Bug reports for the GNU Texinfo documentation system
      • ... Eli Zaretskii
      • ... Gavin Smith
      • ... Eli Zaretskii
      • ... Eli Zaretskii
      • ... Gavin Smith
      • ... pertusus
      • ... pertusus

Reply via email to