Skip Menu |

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 1746
Status: resolved
Priority: 0/
Queue: POE

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

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



Date: Wed, 30 Oct 2002 15:03:07 -0500
From: Rocco Caputo <troc [...] netrus.net>
To: poe [...] perl.org
Cc: bug-POE [...] rt.cpan.org
Subject: Re: Win32 fork+exec not supported error
On Wed, Oct 30, 2002 at 08:36:34PM +0100, Francis Turner wrote: Show quoted text
> Started to play with the samples and got this fairly basic error when > there is a POE::Wheel::Run > > MSWin32 does not fully support fork+exec BEGIN failed--compilation > aborted at c:/Perl/site/lib/POE/Wheel/Run.pm line 63. > > This would seem to kill things dead for now since I rather wanted to do > this.
I suspect fork+exec will work on some versions of Windows, but I won't be able to tell for sure until I have an NT system set up. In the meantime, you might try commenting out the MSWin32 check there. I'm copying this message to bug-POE@rt.cpan.org so it can be tracked. -- Rocco Caputo / troc@pobox.com / poe.perl.org / poe.sf.net
RT-Send-CC: poe [...] perl.org
I tested POE::Wheel::Run on Windows NT 2000 today. It does not work. I was able to work around the problem of exit() in a child "process" quite easily, but the issue of redirecting a child process' stdio through sockets remains. See the Win32 Limitations in IPC::Run's documentation, at http://search.cpan.org/~rsod/IPC-Run-0.79/lib/IPC/Run.pm#Win32_LIMITATIONS at the time of this writing.