Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2023-11-05 Thread Arsen Arsenović
Patrice Dumas writes: > On Sat, Nov 04, 2023 at 02:39:32PM +0100, Arsen Arsenović wrote: >> Afternoon, >> >> Following changes in Texinfo 7.1 (uncertain which commit - haven't >> bisected) FFmpeg documentation no longer builds. This is due to an init >> file (attached). The following is a min

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Gavin Smith
On Sun, Nov 05, 2023 at 09:59:44PM +0200, Eli Zaretskii wrote: > The XS modules are installed in a directory which is usually not > looked into by the dynamic linker. Is that what you are talking > about? If so, we have been using "non-public libraries" since long > ago, no? Or what am I missing

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Eli Zaretskii
> From: Gavin Smith > Date: Sun, 5 Nov 2023 18:12:45 + > Cc: pertu...@free.fr, bug-texinfo@gnu.org > > So you know what a dynamically loaded library is; this contains a collection > of functions and potentially data structures that can be loaded by running > code and run as part of a computer

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Gavin Smith
On Sun, Nov 05, 2023 at 07:52:53PM +0100, Andreas Schwab wrote: > On Nov 05 2023, Gavin Smith wrote: > > > The dynamically loaded libraries used by texi2any (XS modules) are > > completely different. Technically, they are loaded in the same way, > > by the running Perl interpreter. But they are

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Andreas Schwab
On Nov 05 2023, Gavin Smith wrote: > The dynamically loaded libraries used by texi2any (XS modules) are > completely different. Technically, they are loaded in the same way, > by the running Perl interpreter. But they are an integral part of the > texi2any program. They are intended for the use

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Gavin Smith
On Sun, Nov 05, 2023 at 07:38:27PM +0200, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Sun, 5 Nov 2023 17:04:47 + > > > > > Maybe one day libtexinfo could be a public library, but not for now > > > and libtexinfoxs should probably never ever be a public library. > > > > I agree neith

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Eli Zaretskii
> From: Gavin Smith > Date: Sun, 5 Nov 2023 17:04:47 + > > > Maybe one day libtexinfo could be a public library, but not for now > > and libtexinfoxs should probably never ever be a public library. > > I agree neither of them should be a public library now. Can someone please explain what d

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Gavin Smith
On Sun, Nov 05, 2023 at 05:16:44PM +0100, Patrice Dumas wrote: > On Sat, Nov 04, 2023 at 10:58:35PM +, Gavin Smith wrote: > > > > Bingo. /usr/local/lib/libtexinfo.so.0 is being run. It shouldn't even > > be installed directly in /usr/local/lib. > > I could not find a way to make the libtexi

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

2023-11-05 Thread Patrice Dumas
On Sat, Nov 04, 2023 at 10:58:35PM +, Gavin Smith wrote: > > Bingo. /usr/local/lib/libtexinfo.so.0 is being run. It shouldn't even > be installed directly in /usr/local/lib. I could not find a way to make the libtexinfo and libtexinfoxs libraries 'internal' only. Maybe use noinst_LTLIBRARI

Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2023-11-05 Thread Patrice Dumas
On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote: > > Seems that relatively many things changed between 6.x and 7.0. 7.0 was the first release with an official HTML customization API. The API is not stable yet, as the many changes between 7.0 and 7.1 and the changes already in m

Re: Post release texi2any performance regression

2023-11-05 Thread Gavin Smith
On Sun, Nov 05, 2023 at 11:59:11AM +0100, Patrice Dumas wrote: > On Sat, Nov 04, 2023 at 04:06:05PM +, Gavin Smith wrote: > > > At that point, using a new env variable to use perl for > > > structuring/transformations would be very easy based on your patch. > > > If you give a name, I can do it

Re: Post release texi2any performance regression

2023-11-05 Thread Gavin Smith
On Sun, Nov 05, 2023 at 01:01:21PM +0100, Patrice Dumas wrote: > > Indeed, commenting out those lines of code (although it makes the output > > incorrect) appeared to restore the run time to that of 7.1. > > > > This may have been due to a fairly recent change, but the lack of a > > stable, satisf

Re: Post release texi2any performance regression

2023-11-05 Thread Patrice Dumas
On Sat, Nov 04, 2023 at 11:18:59PM +, Gavin Smith wrote: > After comparing results from NYTProf for Texinfo 7.1 and the master > branch with the patch I posted, the remaining possibility that I suspect, > but which I haven't been able to investigate yet due to being stymied > by other problems,

Re: Post release texi2any performance regression

2023-11-05 Thread Patrice Dumas
On Sat, Nov 04, 2023 at 06:53:34PM +, Gavin Smith wrote: > On Sat, Nov 04, 2023 at 04:06:06PM +, Gavin Smith wrote: > > > To me the most likely reason would be that simple_parser has been > > > removed, such that calls of gdt/pgdt from perl are slower. > > > > Thanks, I'll try to investiga

Re: Post release texi2any performance regression

2023-11-05 Thread Patrice Dumas
On Sat, Nov 04, 2023 at 04:06:05PM +, Gavin Smith wrote: > > At that point, using a new env variable to use perl for > > structuring/transformations would be very easy based on your patch. > > If you give a name, I can do it. > > Would TEXINFO_XS_STRUCTURE be ok? Should be done in https://git

Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

2023-11-05 Thread Patrice Dumas
On Sat, Nov 04, 2023 at 02:39:32PM +0100, Arsen Arsenović wrote: > Afternoon, > > Following changes in Texinfo 7.1 (uncertain which commit - haven't > bisected) FFmpeg documentation no longer builds. This is due to an init > file (attached). The following is a minimum reproducer: > > makeinfo