On Mon, Jan 19, 2026 at 06:57:10PM +0100, [email protected] wrote: > On Sat, Jan 17, 2026 at 09:17:24PM +0000, Gavin Smith wrote: > > 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. > > I checked that right now there are two things in $libdir/texinfo, > libraries like libtexinfo*.so*, and Perl XS compiled module files, like > Parser.so. It could be possible to put each of these in a separate > subdirectory, with > - lib/ for libtexinfo*.so* > - XS_extension/ for XS object files > > I think that it would make sense conceptually, I would be in favor of > separating the two, but there is no strict need. > > Any comment? >
I'm indifferent to such a change. My suggestion of using a "lib" subdirectory was only for the benefit of MS-Windows to ensure that all the installed library files were under the $libdir/texi2any hierarchy.
