Re: [EXTERNAL] Re: Issue with Texinfo >=6.8

[Eli Zaretskii]

> From: "Kuberry, Paul Allen" <pakuber@sandia.gov>
> Date: Wed, 14 Dec 2022 18:27:04 +0000
> 
> Between Texinfo 6.7 and 6.8, a change took place where CPPFLAGS is no longer 
> populated in the file tp/Texinfo/XS/Makefile (created from 
> tp/Texinfo/XS/Makefile.in). However, it is populated a few folders up in 
> tp/Makefile (Created from tp/Makefile.in).
> 
> When using `--with-libintl-prefix[=DIR]`, this populates CPPFLAGS. Before 
> 6.8, the value for CPPFLAGS was used in tp/Texinfo/XS. It no longer is, and 
> that is probably because the build system is supposed to be self-contained 
> and not inherit variables from the top-level build system. However,  
> presumably `--with-libintl-prefix` is set because otherwise libintl.h will be 
> missing otherwise. Now when building the XS folder contents, the api.c file 
> is missing a needed include of libintl.h on all machines that don’t come 
> preinstalled with libintl.h in the /usr/include (like Macs).

The change was made AFAIR because the extensions under tp/Texinfo/XS
might need different compilation flags than the C code of the rest of
Texinfo, since the compilation flags for the extensions depend also on
the particular build of Perl you have and how it was built.  For
example, compiling the Perl extension might need an entirely different
compiler and header files, if Perl itself was built with another
compiler.

So now there's a separate set of configure-time variables for tuning
that, which start with "PERL_EXT_".  For example, PERL_EXT_CPPFLAGS
determines the cpp flags for compiling the extensions.  You can use
these variables to pass the necessary libintl-related switches and
other tweaks to the commands that compile the extensions.

If this doesn't satisfy your needs, please tell the details: why you
need to use --with-libintl-prefix, where is your libintl located and
how is it called, etc.