On 2 June 2014 20:51, Andreas Koenig < andreas.koenig.7os6v...@franz.ak.mind.de> wrote:
> demerphq <demer...@gmail.com> writes: > > > I am trying to understand the following failure: > > > > > http://www.cpantesters.org/cpan/report/77c67060-e9e0-11e3-9fed-4ec572305bfd > > > > The output doesn't include the build output so I dont know why this > > failed. > > Just to quote an unnamed fellow perl hacker: spactacles would help. > > Hint: ask your browser to search for "undefined symbol". > > Actually on my laptop that was right off screen, and I didn't notice it. A nicer rendering would make this kind of oversight harder. But my point is still valid, I dont see any *build* output. I see output from make test: Output from '/usr/bin/make test': Running Mkbootstrap for Sereal::Decoder () chmod 644 Decoder.bs PERL_DL_NONLAZY=1 /home/sand/src/perl/repoperls/installed-perls/perl/perl-5.8.5/5da8/bin/perl "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t Can't load '/tmp/loop_over_bdir-2737-IjnvDk/Sereal-Decoder-3.000_003-Tf_394/blib/arch/auto/Sereal/Decoder/Decoder.so' for module Sereal::Decoder: /tmp/loop_over_bdir-2737-IjnvDk/Sereal-Decoder-3.000_003-Tf_394/blib/arch/auto/Sereal/Decoder/Decoder.so: undefined symbol: HvRITER_set at /home/sand/src/perl/repoperls/installed-perls/perl/perl-5.8.5/5da8/lib/5.8.5/x86_64-linux/DynaLoader.pm line 230. at t/001_load.t line 4. That doesnt show me the normal build output I expect to see when building Sereal::Decoder, like this from 5.8.9: $ make Skip blib/lib/Sereal/Performance.pm (unchanged) Skip blib/lib/Sereal/Decoder/Constants.pm (unchanged) cp lib/Sereal/Decoder.pm blib/lib/Sereal/Decoder.pm cc -c -I. -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -Wall -W -DVERSION=\"3.000_003\" -DXS_VERSION=\"3.000_003\" -fPIC "-I/home/yorton/perl5/perlbrew/perls/perl-5.8.9/lib/5.8.9/x86_64-linux/CORE" -DNDEBUG Decoder.c Decoder.c: In function ‘XS_Sereal__Decoder__Constants_constant’: ./const-xs.inc:38:11: warning: ‘iv’ may be used uninitialized in this function [-Wmaybe-uninitialized] ./const-xs.inc:11:6: note: ‘iv’ was declared here cc -c -I. -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -Wall -W -DVERSION=\"3.000_003\" -DXS_VERSION=\"3.000_003\" -fPIC "-I/home/yorton/perl5/perlbrew/perls/perl-5.8.9/lib/5.8.9/x86_64-linux/CORE" -DNDEBUG miniz.c cc -c -I. -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -Wall -W -DVERSION=\"3.000_003\" -DXS_VERSION=\"3.000_003\" -fPIC "-I/home/yorton/perl5/perlbrew/perls/perl-5.8.9/lib/5.8.9/x86_64-linux/CORE" -DNDEBUG srl_decoder.c srl_decoder.c:1550:12: note: #pragma message: OLD_REGEXP In file included from srl_decoder.c:51:0: ptable.h:249:1: warning: ‘PTABLE_delete’ defined but not used [-Wunused-function] ptable.h:217:1: warning: ‘PTABLE_clear_dec’ defined but not used [-Wunused-function] srl_decoder.c:177:1: warning: ‘srl_ptable_debug_dump’ defined but not used [-Wunused-function] Running Mkbootstrap for Sereal::Decoder () chmod 644 Decoder.bs rm -f blib/arch/auto/Sereal/Decoder/Decoder.so cc -shared -O2 -L/usr/local/lib Decoder.o miniz.o srl_decoder.o -o blib/arch/auto/Sereal/Decoder/Decoder.so \ \ chmod 755 blib/arch/auto/Sereal/Decoder/Decoder.so cp Decoder.bs blib/arch/auto/Sereal/Decoder/Decoder.bs chmod 644 blib/arch/auto/Sereal/Decoder/Decoder.bs Manifying blib/man3/Sereal::Performance.3 lib/Sereal/Performance.pm:8: Unknown command paragraph "=encoding utf8" Manifying blib/man3/Sereal::Decoder.3 lib/Sereal/Decoder.pm:34: Unknown command paragraph "=encoding utf8" Note those #pragma message lines, I am outputting useful diagnostics output that are not included in the cpantesters failure report. > > Similarly when I get CPAN-Testers test failure reports they tell me only > what > > test *files* failed, but do not give me verbose test output of the > > failures. > > Whenever this is the case, you do have the option to fix it. Why do you > believe that the tester is more qualified to debug this than you? > I don't understand your question. I am not asking that the tester debug anything, just that when my tests fail they send me the *verbose* failure output which contains valuable context on what failed which helps me debug my code, just as I would like to see the *full* build output, and not just the results from make test. I don't get why you are being snarky here actually. All I am trying to do is fix my software to run in one of your (that is you Andreas) test environments, for a version of Perl which I don't even use. I even thought about just following the instructions to disable 5.8.5, but I thought since the report came from you (that is you personally Andreas) that I might as well make an effort to fix it. So I am little bewildered about the tone. What have I done wrong? cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
