On 17/08/2013 23:46, D. Barbier wrote:
If I read your log file right, there are several issues here:
* Your Perl spits out several warnings (not fatal, but annoying). I
just pushed a commit to fix these warnings.
* Sgml tests fail because you use opensp instead of James Clark's
sp. I cannot reproduce your issue when installing opensp.
* Html tests fail because there is no Html.pm module in your
tarball. This is strange, Html.pm is indeed not shipped in tarballs
(it is considered as experimental and not fully supported), but
associated test files should also be absent. Run './Build dist' to
build the tarball, this should solve this issue.
* TeX tests fail. I do not see what happens. Can you please run
cd t && LC_ALL=C perl ../po4a-gettextize -f latex -m data-24/simple.tex
and send output?
I downgraded perl, now perl -v now reports:
This is perl 5, version 14, subversion 4 (v5.14.4) built for x86_64-linux-thread-multi
I pulled trunk with following command:
svn checkout svn://anonscm.debian.org/po4a/trunk
-> Revision 2733 extracted
output of "cd t && LC_ALL=C perl ../po4a-gettextize -f latex -m
Can't locate Locale/Po4a/Chooser.pm in @INC (@INC contains: /usr/local/lib64/perl5
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl
/usr/lib64/perl5 /usr/share/perl5 .) at ../po4a-gettextize line 165.
BEGIN failed--compilation aborted at ../po4a-gettextize line 165.
That's right, I don't have Locale/Po4a/Chooser.pm in any of these locations. But
how could it be there as po4a is not installed yet?
./Build dist fails (see attached log_Build_dist) as this target implies running the tests,
Any way to simply exclude experimental modules and associated test from a tarball (that I
can make myself)?
I couldn't find a way to build sp-1.3.4 (see attached log_pm-1.3.4), I would need help
Maybe it's a compatibility problem with my gtcc version (4.8.1) or the Makefile needs
a tuning that I'm not able to determine.
Maybe there is a Debian patch that allows building to succeed, but I couldn't find
one. Could you help me to locate one, if any?
Anyway I did run again ./Build -verbose=1 --debug=1 then ./Build test-verbose=1 --debug=1
and output are attached, as Build_log and Build_test_log respectively.
At least Tex tests don't fail anymore (and I don't care for html failing).