On Mon, Jul 21, 2025 at 10:29:24PM +0100, Gavin Smith wrote:
> > Is the mandatory dependency on libperl intended?
> > 
> > Bruno
> 
> It shouldn't depend on libperl.  As far as I understand, libperl can come
> in two ways (Patrice could confirm this).
> 
> The first is when building the C implementation of texi2any (known as
> ctexi2any), but this is not used by default, because of this dependency
> which is often not present.

Indeed.  In that case, there is an autoconf test in tta/configure.ac, so
a missing libperl should be taken into account, and even if the C
texi2any was the default, the Perl texi2any would be used if liberl was
missing.

> The second is as a result of the SWIG stuff, which looks like is
> happening here.

Indeed, there is no proper check of libperl being present, while it is
needed to link the Python shared object with the Texinfo code.  Note
that there is no check either on platforms that need to be linked with
--no-undefined and also need libperl.

So, it would be good to add an autoconf check similar to the one
checking for the possibility to embed Perl.  I'll probably do it when I
have time. 

> I have not looked into what is being done with SWIG, but hopefully if
> you reconfigure with "./configure --without-swig", some of the SWIG
> parts of the build will be omitted and this error won't occur.

Indeed, you are right.

-- 
Pat

  • depe... Bruno Haible via Bug reports for the GNU Texinfo documentation system
    • ... Gavin Smith
      • ... Patrice Dumas
        • ... Bruno Haible via Bug reports for the GNU Texinfo documentation system
        • ... Patrice Dumas
          • ... Bruno Haible via Bug reports for the GNU Texinfo documentation system

Reply via email to