On Sun, Apr 30, 2017 at 05:37:53PM +0300, Eli Zaretskii wrote: > > Date: Sat, 29 Apr 2017 11:18:33 +0300 > > From: Eli Zaretskii <[email protected]> > > Cc: [email protected] > > > > > 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. > > Heh, when I run the above, everything is OK: > > cd tp/Texinfo/Convert/XSParagraph/ > TEXINFO_XS=debug /C/Perl/bin/perl -I ../../.. -I . fail.pl > checking ../../../TestXS.la > checking ./TestXS.la > found ./TestXS.la > ./.libs/TestXS.dll loaded > looking for boot_TestXS > trying to call boot_TestXS... > ...succeeded > message from XS module > > which is identical to your output. > > Moreover, re-running the configure script with TEXINFO_XS=debug on the > command line causes it to successfully detect that XS extensions can > be built!
This is weird indeed. Just to confirm, running /C/Perl/bin/perl -I ../../.. -I . fail.pl doesn't load the module either? What about TEXINFO_XS=default /C/Perl/bin/perl -I ../../.. -I . fail.pl The only idea I have is that you have TEXINFO_XS already set to "omit" in your environment.
