Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-07 Thread Igor Pechtchanski
On Fri, 8 Jul 2005, Angelo Graziosi wrote: > Last morning I have made a build of ROOT (a CERN application) using the > snapshot 20050705, bash-3.0-3-test, ash-20040127-1, coreutils-5.3.0-6 > GCC-3.3.3-3. The buid takes almost 1.5 h > > After upgrading to bash-3.0-7, ash-20040127-3, coreutils-5.3.0

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-07 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Pechtchanski on 7/7/2005 6:34 PM: > I suspect this may actually be a bug in bash, since single > quotes ought to stop it from trying to expand variable references. This > only happens when the single quotes are inside a shell substit

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-07 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Pechtchanski on 7/7/2005 6:34 PM: > Yep. The new /bin/sh is bash. Apparently, bash doesn't like the > following line: > > if [ "`echo $dllname | sed 's{^lib/.*\.dll${{'`" != "$dllname" ]; then > > because in bash, ${ has special m

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-08 Thread Angelo Graziosi
On Thu, 7 Jul 2005, Igor Pechtchanski wrote: > On Fri, 8 Jul 2005, Angelo Graziosi wrote: > > > Last morning I have made a build of ROOT (a CERN application) using the > > snapshot 20050705, bash-3.0-3-test, ash-20040127-1, coreutils-5.3.0-6 > > GCC-3.3.3-3. The buid takes almost 1.5 h > > > >

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-08 Thread Eric Blake
> > Yep. The new /bin/sh is bash. Apparently, bash doesn't like the > > following line: > > > > if [ "`echo $dllname | sed 's{^lib/.*\.dll${{'`" != "$dllname" ]; then > > > Downgrading a package at time, I have seen that reinstalling > ash-20040127-1 (and using Bash-3.0-7, coreutils-5.3.0-7) al

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-08 Thread Angelo Graziosi
On Fri, 8 Jul 2005, Eric Blake wrote: > ... > > Meanwhile, you will have to wait patiently until the upstream > maintainer releases a patch (because I haven't the faintest clue > where in the lexer to look for fixing his parse error). Repeated > pinging on the cygwin list will not help speed

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-10 Thread Lev Bishop
On 08/07/05, Eric Blake wrote: > Meanwhile, you will have to wait patiently until the upstream > maintainer releases a patch (because I haven't the faintest clue > where in the lexer to look for fixing his parse error). Repeated > pinging on the cygwin list will not help speed up the situation.

Re: Problems with ash-20040127-3 (Attn: bash maintainer)

2005-07-10 Thread Igor Pechtchanski
On Sun, 10 Jul 2005, Lev Bishop wrote: > On 08/07/05, Eric Blake wrote: > > Meanwhile, you will have to wait patiently until the upstream > > maintainer releases a patch (because I haven't the faintest clue > > where in the lexer to look for fixing his parse error). Repeated > > pinging on the c