I successfully built and tested Perl 5.20.0 on Darwin/PPC when it was
released two months ago. I built and tested blead today for the first
time since then. I was surprised to get a test failure in
t/porting/libperl.c.
When I re-directed the test's STDOUT and STDERR to a file, I got a
tremendous amount of "# Unexpected nm output" lines. For the full
output, see the tarball attached.
Here is the short version of the output.
#####
$ cd t;./perl harness -v porting/libperl.t ; cd -# Failed test 2 - has
text Perl_peep at porting/libperl.t line 196
# Failed test 3 - has text Perl_pp_uc in pp.o at porting/libperl.t line 197
# Failed test 4 - has data const symbols at porting/libperl.t line 198
# Failed test 5 - has PL_no_mem at porting/libperl.t line 199
# Failed test 6 - has PL_hash_seed at porting/libperl.t line 325
# Failed test 7 - has PL_ppaddr at porting/libperl.t line 326
ok 1 - has object pp.o
not ok 2 - has text Perl_peep
not ok 3 - has text Perl_pp_uc in pp.o
not ok 4 - has data const symbols
not ok 5 - has PL_no_mem
not ok 6 - has PL_hash_seed
not ok 7 - has PL_ppaddr
ok 8 - has no PL_VarsPtr
ok 9 - has no PL_Vars
ok 10 - has no Perl_GetVars
Failed 6/10 subtests
Test Summary Report
-------------------
porting/libperl.t (Wstat: 0 Tests: 10 Failed: 6)
Failed tests: 2-7
Files=1, Tests=10, 3 wallclock secs ( 1.87 usr 0.12 sys + 0.22 cusr
0.07 csys = 2.28 CPU)
Result: FAIL
/Users/jimk/gitwork/perl
#####
I am not getting this failure on Linux x86_64. I have not yet tried
this on Darwin x86_64.
Has anything happened lately that would have an impact on this?
Thank you very much.
Jim Keenan
