BUG: format_line_message: error_location_info undef

On Thu, Aug 15, 2024 at 11:51:10PM +0200, Dario Gjorgjevski wrote: > > You say that TEXINFO_XS=debug does not show anything useful but it would > > still be helpful to see exactly how far it got successfully before failing. > > Here is the output: Is there something missing from this, as in a pre

Re: Can't build current HEAD with --enable-perl-xs on macOS

Hi, Gavin, On Thu, Aug 15, 2024 at 8:49 PM Gavin Smith wrote: > > There is a possibility that the XS modules were disabled and then > after this commit, they started being run, revealing the error. > Did "TEXINFO_XS=required texi2any ..." work before that commit? Yes, it works just fine. I have

Re: fix an error message during configure

On Wed, Aug 14, 2024 at 07:24:43PM +0200, Bruno Haible wrote: > Gavin Smith wrote: > > I'm not sure applying a patch such as this is the best way to upgrade > > these files. If these files came from Automake then it would make sense > > to update them from the Automake release with an installed ve

Re: Can't build current HEAD with --enable-perl-xs on macOS

On Thu, Aug 15, 2024 at 03:59:23PM +0200, Dario Gjorgjevski wrote: > Building on macOS with --enable-perl-xs fails with: > > $ TEXINFO_DEV_SOURCE=1 top_srcdir="$(top_srcdir)" > top_builddir="$(top_builddir)" $(PERL) ../../tp/texi2any.pl -o > texi2any_internals.info texi2any_internals.texi >

Can't build current HEAD with --enable-perl-xs on macOS

Building on macOS with --enable-perl-xs fails with: $ TEXINFO_DEV_SOURCE=1 top_srcdir="$(top_srcdir)" top_builddir="$(top_builddir)" $(PERL) ../../tp/texi2any.pl -o texi2any_internals.info texi2any_internals.texi dyld[99271]: dyld_image_path_containing_address(0x10d5c7000) => '$(top_buildd