X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date: Thu, 8 Apr 1999 11:53:17 +0200 (MET DST)
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender: broeker AT acp3bf
To: djgpp-workers AT delorie DOT com
cc: Gurunandan R Bhat <grbhat AT unigoa DOT ernet DOT in>
Subject: Re: Can (was Re: Cannot) build linux-x-dos cross-compiler
In-Reply-To: <Pine.SUN.3.91.990405083842.26011A-100000@is>
Message-ID: <Pine.LNX.3.93.990408114819.200A-100000@acp3bf>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers 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, 5 Apr 1999, Eli Zaretskii wrote:

> On Sun, 4 Apr 1999, Gurunandan R Bhat wrote:
> 
> > 1. ldscripts are incorrectly built if I use bash2.0 (on SuSE 5.3). The
> >    genscripts.sh adds multiple braces. I solved this by reverting back to
> >    bash1.

> Please report any details you can supply about this problem.  You might 
> have found a bug in Bash 2 which is currently in beta testing.  Be sure 
> to report the date of bash.exe.

I had observed the same problem (also with SuSE 5.3) with building a
Linux-to-DJGPP cross compiler. Switching to bash1 works around the
problem, but the real bug is in the script that generates the ldscripts. I
can't remember the details off-hand, but I recall my conclusion at the
time to have been that the ldscript generator, a sh script, only ever
worked because bash *1* had a bug in its handling of nested ${var:value}
constructs containing additional '{' or '}' characters. 

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.