Date: Mon, 10 Sep 2001 18:52:03 +0200 From: Laszlo Molnar To: djgpp-workers AT delorie DOT com Cc: "'Perl 5 Porters'" Subject: Re: Win2k + djgpp Message-ID: <20010910185203.B3069@libra.eth.ericsson.se> References: <20010910163219 DOT 4AE6 DOT H DOT M DOT BRAND AT hccnet DOT nl> <001201c13a17$20353020$747d76d5 AT pandora DOT be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <001201c13a17$20353020$747d76d5@pandora.be>; from tim.van.holder@pandora.be on Mon, Sep 10, 2001 at 06:39:13PM +0200 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, Sep 10, 2001 at 06:39:13PM +0200, Tim Van Holder wrote: [...] > There's a known problem with file descriptors perl-spawned > programs (present in 5.6.0, 5.6.1 and 5.7.2), which prevents > autoconf > 2.50 from functioning under DJGPP. I've yet to find > either cause or solution (Laszlo, you have any idea?). A test > case is attached - run normally, foo.exe will allocated > FDs 5 - 19 for the testfiles; if run from the perl script, it > gets FDs 3 - 17 (and 3 and 4 are not supposed to be used, IIRC). > It _might_ be something else though (perhaps another Win2K quirk). Perl starts with closing stdprn and stdaux (#ifdef MSDOS). Should it leave them open? Laszlo