On Wednesday 08 November 2006 11:44, Steve [Gentoo] wrote:
> Thanks for your help, and while it might not have been obvious to you
> (or anyone else reading along)... everything that was confusing before
> is clear now... to me at least.  While I can see what is wrong, it isn't
> 100% clear if it constitutes a bug or not.
>
> The problem is that the configure script starts '#!/bin/sh' - but goes
> on to depend upon Bash specific features... specifically substitution.
> I expect this would not be a problem for most users where /bin/sh is a
> sym-link to /bin/bash.... but, for me, /bin/sh was a sym-link to
> /bin/ash... and, for that shell, line 151 is invalid.

Heh, I just hadn't noticed that the first line of the script said /bin/sh. 
That's definitely a bug. Either the script must be modified to only 
use /bin/sh features or it must request a shell that supports it...

-- 
Bo Andresen