Skip Menu |

This queue is for tickets about the prefork CPAN distribution.

Report information
The Basics
Id: 47559
Status: resolved
Priority: 0/
Queue: prefork

People
Owner: Nobody in particular
Requestors: bobtfish [...] bobtfish.net
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: 1.04



Subject: Config_heavy.pl not shipped in some perl versions
CPAN::Reporter: make result is 'pass', No errors. ADAMK/prefork-1.03.tar.gz /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/01_compile.t .. ok Can't locate Config_heavy.pl in @INC (@INC contains: /Users/t0m/.cpan/build/prefork-1.03-MR85f6/inc /Users/t0m/.cpan/build/prefork-1.03-MR85f6/blib/lib /Users/t0m/.cpan/build/prefork-1.03-MR85f6/blib/arch /Users/t0m/perl5/lib/perl5/darwin-thread-multi-2level /Users/t0m/perl5/lib/perl5/darwin-thread-multi-2level /Users/t0m/perl5/lib/perl5 /opt/subversion/lib/svn-perl /Users/t0m/perl5/lib/perl5/darwin-thread-multi-2level /Users/t0m/perl5/lib/perl5 /Users/t0m/perl5/lib/perl5/darwin-thread-multi-2level /opt/subversion/lib/svn-perl /System/Library/Perl/5.8.6/darwin-thread-multi-2level /System/Library/Perl/5.8.6 /Library/Perl/5.8.6/darwin-thread-multi-2level /Library/Perl/5.8.6 /Library/Perl /Network/Library/Perl/5.8.6/darwin-thread-multi-2level /Network/Library/Perl/5.8.6 /Network/Library/Perl /System/Library/Perl/Extras/5.8.6/darwin-thread-multi-2level /System/Library/Perl/Extras/5.8.6 /Library/Perl/5.8.1 .) at /Users/t0m/.cpan/build/prefork-1.03-MR85f6/blib/lib/prefork.pm line 200. # Looks like you planned 18 tests but ran 4. # Looks like your test exited with 2 just after 4. The perl shipped by Apple in MacOS Tiger (10.4) doesn't include Config_heavy.pl, an therefore prefork fails to install. I think that requiring Config_heavy.pl should be executed in an eval {} block, to avoid this issue on systems which don't have Config_heavy.pl
This was fixed in 1.04 (2009-07-12, 9 years ago, and only 8 days after this bug was reported!)