Front page | perl.perl5.porters |
Postings from June 2019
On Fri, Jun 7, 2019 at 2:33 PM James E Keenan via RT <perlbug-followup@perl.org> wrote: > > On Fri, 07 Jun 2019 19:15:35 GMT, randir wrote: > > This is a bug report for perl from sergey.aleynikov@gmail.com, > > generated with the help of perlbug 1.41 running under perl 5.31.1. > > > > > > ----------------------------------------------------------------- > > [Please describe your issue here] > > > > m-catalina:t/ (blead) λ ./perl harness porting/libperl.t > > porting/libperl.t .. 1/? porting/libperl.t: Unexpected /usr/bin/nm > > error: no symbols > > porting/libperl.t: Unexpected /usr/bin/nm errors > > porting/libperl.t .. Dubious, test returned 255 (wstat 65280, 0xff00) > > All 35 subtests passed > > > > Test Summary Report > > ------------------- > > porting/libperl.t (Wstat: 65280 Tests: 35 Failed: 0) > > Non-zero exit status: 255 > > Parse errors: No plan found in TAP output > > Files=1, Tests=35, 0 wallclock secs ( 0.36 usr 0.00 sys + 0.13 cusr > > 0.03 csys = 0.52 CPU) > > Result: FAIL > > > > Am I correct in thinking that Catalina is the latest version of Mac OS X? It won't be out until the fall. He must have a developer preview. Among other changes, the system volume is read-only in Catalina and the default shell is zsh rather than bash. More likely, though, is some change to the formatting or wording of nm output. Figuring out the exact nm command libperl.t is running (using the Perl debugger as James suggested) and then running it external to Perl and seeing what its output looks like and how it might differ from what the test expects might be the best place to start.Thread Previous | Thread Next