Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the YAML CPAN distribution.

Report information
The Basics
Id: 14481
Status: resolved
Priority: 0/
Queue: YAML

People
Owner: Nobody in particular
Requestors: njh [...] bandsman.co.uk
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.49_01
Fixed in: 0.70



Subject: Fails to install on MACOS/X
[snip] cp lib/YAML/Family.pm blib/lib/YAML/Family.pm cp lib/YAML.pm blib/lib/YAML.pm cp lib/YAML/Error.pm blib/lib/YAML/Error.pm cp lib/YAML/Transfer.pm blib/lib/YAML/Transfer.pm cp ysh blib/script/ysh /usr/bin/perl -Iinc "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/ysh Manifying blib/man3/YAML::Node.3 Manifying blib/man3/YAML.3 Manifying blib/man1/ysh.1 /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t t/00basic.....ok t/01pass......ok t/02fail......ok t/10dump......ok t/11code......FAILED tests 1-2, 5 Failed 3/5 tests, 40.00% okay t/12nest......ok t/13opts......ok t/20load......ok t/21spec......ok t/22slides....ok t/30errors....ok t/test1.......ok Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------------- t/11code.t 5 3 60.00% 1-2 5 Failed 1/12 test scripts, 91.67% okay. 3/277 subtests failed, 98.92% okay. make: *** [test_dynamic] Error 35 /usr/bin/make test -- NOT OK Running make install make test had returned bad status, won't install without force Show quoted text
cpan>
Sep. 05 14:36:21 2005, guest wrote Show quoted text
> Fails to install on MACOS/X
Show quoted text
> Failed 1/12 test scripts, 91.67% okay. 3/277 subtests failed, 98.92%
Please test version 0.70. Cpantesters reports ( http://matrix.cpantesters.org/?dist=YAML+0.70 ) are ok for this version.. -- Alexandr Ciornii, http://chorny.net
This issue has been copied to: https://github.com/ingydotnet/yaml-pm/issues/50 please take all future correspondence there. This ticket will remain open but please do not reply here. This ticket will be closed when the github issue is dealt with.
Seems to be fixed, closing