From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: <djgpp-workers AT delorie DOT com>
Subject: RE: FD 4 special for DJGPP (and Perl in particular)?
Date: Wed, 28 Feb 2001 21:39:17 +0100
Message-ID: <CAEGKOHJKAAFPKOCLHDIEECCCBAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <9743-Wed28Feb2001221849+0200-eliz@is.elta.co.il>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

> I might be missing something--if Perl is built using stock v2.03 libc,
> how come any close-on-exec issue could be relevant?  That version of
> the library didn't support any close-on-exec stuff.
Don't know - the error at hand seemed like it could be related to
such things, which is why I asked. If 2.03 libc has no support, that may
be the cause (I seem to recall that CVS thought support was there, so
maybe perl does too and, unlike CVS, doesn't crap out if the function
call fails).
I'll try updating my DJGPP CVS tree and linking perl against the CVS libc.