On Mon, Nov 17, 2025 at 12:24:01AM +0100, Patrice Dumas wrote:
> > Could it help to use a subset of PERL_EXTUTILS_EMBED_ccopts instead for
> > ctexi2any_CPPFLAGS?
>
> Possibly, or for CFLAGS only. I wanted to use ExtUtils::Embed as is to
> follow the documentations on embedding Perl, but we can also do
> something cleaner by ourselves. My feeling is that it should work, I'll
> have a try.
It worked for Alma Linux and it is cleaner now, since the Perl include
directory is not present anymore for the comilation, which is an
improvement.
It didn't work for OpenCSW. With the new change, the Perl include
directory is not present anymore, but there are other include
directories -I options in $Config{ccflags}, which are still present.
Then what you described happens, there is an inconsistency between the
configure test detection of libintl (in the libc) with empty CFLAGS and
the libintl.h included with $Config{ccflags}, which is an external
libintl (and most likely the GNU one).
One possibility could be to use $Config{ccflags} for all the
compilations, including the "Pure C" ones (which could be what you were
advocating in your mail). It could bring in more consistency between
compilation and linking. There would also be a risk that the flags
in $Config{ccflags} bring in something incompatible with gnulib/autoconf
config.h and other headers, but we can try and see. Another drawback is
that it is harder for the user to override the Perl cflags for "Pure C".
I'll try that unless there is another proposal.
--
Pat
