> From: Gavin Smith <[email protected]> > Date: Sat, 29 Apr 2017 08:57:12 +0100 > Cc: [email protected] > > > I cannote figure out why it reaches this conclusion: the TestXS module > > is built successfully. How can I find out why the detection fails? > > You could try going into the tp/Texinfo/Convert/XSParagraph subdirectory > and running > > TEXINFO_XS=debug ${PERL} -I ../../../ -I . fail.pl > > where ${PERL} is the path to your Perl executable.
Thanks, will do. When the equivalent command runs as part of the configure script, which Perl is invoked here? Is it the one specified with PERL= when the configure script was invoked, or is it the one found on PATH? It should be the former.
