Wed Sep 09 04:44:03 2009: Request 49508 was acted upon.
Transaction: Correspondence added by sisyph...@optusnet.com.au
Queue: Win32-Process
Subject: Re: [rt.cpan.org #49508] CPAN build fails in Strawberry Perl
5.8.9.2
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: da...@nadle.com
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=49508 >
----- Original Message -----
From: "David L. Nadle via RT" <bug-win32-proc...@rt.cpan.org>
>
> C:\strawberry\perl\bin\perl.exe -IC:\strawberry\perl\lib
> -IC:\strawberry\perl\lib C:\strawberry\perl\lib\ExtUtils\xsubpp -typemap
> C:\strawberry\perl\lib\ExtUtils\typemap -typemap typemap Process.xs
> >xstmp.c &&
> C:\strawberry\perl\bin\perl.exe -MExtUtils::Command -e "mv" -- xstmp.c
> Process.cpp
Yep - I get the same as the above. So where does 'Process.c' come from ?
> Process.c: In function `void boot_Win32__Process(PerlInterpreter*,
> CV*)':
I can find a 'Process.cpp' in my build, but not a 'Process.c'.
Very strange - unfortunately, I don't have the exact same strawberry build
as you. I have strawberry-5.10.0, along with a couple of other mingw-built
perls (including perl-5.8.9). None of them create a 'Process.c' when
building Win32::Process. And they all build Win32::Process-0.14 just fine.
Cheers,
Rob.
