Skip Menu |

This queue is for tickets about the Devel-REPL CPAN distribution.

Report information
The Basics
Id: 43106
Status: resolved
Priority: 0/
Queue: Devel-REPL

People
Owner: OLIVER [...] cpan.org
Requestors: BROQ [...] cpan.org
Cc:
AdminCc:

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



Subject: Devel::REPL::Plugin::ReadLineHistory compile issues under Strawberry
When trying to install Devel::REPL under Strawberry Perl this error occurs during make test: C:\strawberry\perl\bin\perl.exe "-Iinc" Makefile.PL --config= --installdeps=Moos e,0.64,MooseX::Object::Pluggable,0.0009,MooseX::Getopt,0.15,MooseX::AttributeHel pers,0.14,B::Keywords,0,Lexical::Persistence,0 C:\strawberry\perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib\lib', 'blib\arch')" t/load_core.t t/load_core....1/? # Failed test 'use Devel::REPL::Plugin::ReadLineHistory;' # at t/load_core.t line 17. # Tried to use 'Devel::REPL::Plugin::ReadLineHistory'. # Error: The getpwuid function is unimplemented at C:\strawberry\cpan\build \Devel-REPL-1.003002-9hIhHW\blib\lib/Devel/REPL/Plugin/ReadLineHistory.pm line 1 0. # Compilation failed in require at (eval 259) line 2. # BEGIN failed--compilation aborted at (eval 259) line 2. # Looks like you failed 1 test of 16. t/load_core.... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/16 subtests And here's the perl version info: C:\strawberry\cpan\build\Devel-REPL-1.003002-9hIhHW>perl -v This is perl, v5.10.0 built for MSWin32-x86-multi-thread A quick patch using File::HomeDir rather than relying getpwuid seems to do the trick (attahced). Cheers, Dan B aka broquaint
Subject: ReadLineHistory.pm.diff
8a9 > use File::HomeDir; 11c12 < (($ENV{HOME} || (getpwuid($<))[7]) . "/.perlreplhist"); --- > (File::HomeDir->my_home . "/.perlreplhist");
Hi, On Sat Feb 07 08:27:45 2009, BROQ wrote: Show quoted text
> When trying to install Devel::REPL under Strawberry Perl this error > occurs during make test: > > # Error: The getpwuid function is unimplemented at
Many thanks indeed for the bug report and patch. Fix applied and should be in the next release 1.3.3. regards, oliver.