Opened 21 months ago

Last modified 21 months ago

#50957 new defect

panda: broken on 10.6

Reported by: mojca (Mojca Miklavec) Owned by: coke (Will Coleda)
Priority: Normal Milestone:
Component: ports Version:
Keywords: snowleopard Cc:
Port: panda

Description (last modified by mojca (Mojca Miklavec))

See the log:

cd "/path/to/build/panda-2016.02" && /opt/local/bin/perl6 bootstrap.pl --prefix=/opt/local
==> Bootstrapping Panda
==> Installing panda from a local directory '/path/to/build/panda-2016.02'
==> panda depends on File::Find, Shell::Command, JSON::Fast
==> Shell::Command depends on File::Find
==> Fetching File::Find
==> Building File::Find
==> Testing File::Find
Unknown option: e
Unknown option: norc
test stage failed for File::Find: Tests failed
  in method install at /path/to/build/panda-2016.02/lib/Panda.pm line 157
  in block  at /path/to/build/panda-2016.02/lib/Panda.pm line 229
  in method resolve at /path/to/build/panda-2016.02/lib/Panda.pm line 223
  in sub MAIN at bin/panda line 18
  in block <unit> at bin/panda line 150

Failure Summary
----------------
/path/to/build/panda-2016.02(
  *test stage failed for File::Find: Tests failed)
The spawned process exited unsuccessfully (exit code: 1)
  in sub MAIN at bootstrap.pl line 66
  in block <unit> at bootstrap.pl line 8

See also comment:4:ticket:50158. It makes more sense to treat this separately from other problems with Panda.

Change History (3)

comment:1 Changed 21 months ago by mojca (Mojca Miklavec)

  • Description modified (diff)

comment:2 Changed 21 months ago by geekosaur

That's the "prove" command failing. I haven't had a 10.6 system available in years so don't know if there's a "prove" other than the Perl 5 one around, but that's what it looks like to me.

comment:3 Changed 21 months ago by mojca (Mojca Miklavec)

There is:

> /usr/bin/prove --version
prove v2.64, using Test::Harness v2.64 and Perl v5.10.0

The perl 5.22 from MacPorts with

> prove --version
TAP::Harness v3.35 and Perl v5.22.1

is present at the time of the build, but perhaps the wrong binary gets called?

Note: See TracTickets for help on using tickets.