Front page | perl.perl5.porters |
Postings from June 2019
On Fri, Jun 07, 2019 at 04:22:57PM -0500, Craig A. Berry wrote:
> 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.
Running the text script manually shows, on line 8, how nm was invoked:
$ ./perl -Ilib t/porting/libperl.t
# $^O = linux
# $Config{archname} = x86_64-linux-thread-multi
# $Config{cc} = cc
# libperl = ../libperl.a
# nm = /usr/bin/nm
# nm_style = gnu
# nm_opt =
# command: "/usr/bin/nm ../libperl.a 2>libperl20767 |"
ok 1 - has object pp.o
....
--
All wight. I will give you one more chance. This time, I want to hear
no Wubens. No Weginalds. No Wudolf the wed-nosed weindeers.
-- Life of Brian
Thread Previous
|
Thread Next