X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Subject: Re: A buffering problem?
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: djgpp-workers AT delorie DOT com
Cc: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
In-Reply-To: <20011212104930.D9145@libra.eth.ericsson.se>
References: <20011212104930 DOT D9145 AT libra DOT eth DOT ericsson DOT se>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0 (Preview Release)
Date: 12 Dec 2001 11:53:13 +0100
Message-Id: <1008154396.27038.1.camel@bender.falconsoft.be>
Mime-Version: 1.0
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 Wed, 2001-12-12 at 10:49, Laszlo Molnar wrote:
> Hi Workers!
> 
> I'm currently working on the would-be perl 5.8.0 port, and
> unfortunately I see 60+ test failures with this version. It seems ~50
> of them are caused by some strange buffering problem. Before I start
> debugging it, I'd like to ask whether someone noticed similar problems
> earlier with 2.03? It seems to be connected to heavy redirection of
> file handles...
> 
> Thanks for any hints, Laszlo

I would guess this is the same issue that prevented autoconf 2.52 and
higher to work under DJGPP.  If so, the culprit is perl.c, which closes
stdprn.  This causes programs run by perl to recycle fd 3, but the exit
code won't close (and flush) that fd properly because it thinks that it
is stdprn.  Simply not closing stdprn fixed this (and made autoconf 2.52
work.