Date: Mon, 10 Sep 2001 23:31:19 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Tim Van Holder" Message-Id: <7458-Mon10Sep2001233119+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: djgpp-workers AT delorie DOT com, perl5-porters AT perl DOT org In-reply-to: <001201c13a17$20353020$747d76d5@pandora.be> (tim DOT van DOT holder AT pandora DOT be) Subject: Re: Win2k + djgpp References: <001201c13a17$20353020$747d76d5 AT pandora DOT be> 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 > From: "Tim Van Holder" > Date: Mon, 10 Sep 2001 18:39:13 +0200 > > > > base/cond......c:/util/djgpp/tmp/dj310000: Cannot duplicate > > fd 1: Bad file descriptor (EBADF) > > FAILED at test 0 > > 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). Why is this a problem, and how does it cause the EBADF failure? I don't think a program (Perl in this case) should assume anything about the descriptors that are preconnected, beyond the standard 3 ones.