Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <39987229.2CB876B3@phekda.freeserve.co.uk>
Date: Mon, 14 Aug 2000 23:26:49 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: "Mark E." <snowball3 AT bigfoot DOT com>
CC: djgpp-workers AT delorie DOT com
Subject: Re: Problems with depcomp from fileutils 4.0x & bash 2.03
References: <39982FBF DOT 32711 DOT 231F56 AT localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

"Mark E." wrote:
> 
> > down to bash 2.03 (thanks guys!). This is actually a problem earlier
> > encountered in the djgpp-workers thread "Porting problems with
> > Sh-utils (beta)" - the first mail is dated Sat, 8 Apr 2000 18:49:49
> > +0500 on my system.
> 
> This is occasionally to gnu.bash.bug. The Bash maintainer's response
> always is that the construct is working as intended.

But I think this is a bug in the DJGPP port of bash 2.03. An equivalent
test under Linux works fine.

If this behaviour was the expected behaviour of bash 2.03, then how could
anybody build fileutils 4.0x under Linux, etc.? In fact, I just tried it
myself and the fileutils 4.0x compile worked with bash 2.03. This seems to
support my suspicion of a bug in the DJGPP port.

Thanks, bye,

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]