| 1 |
On Wednesday 08 November 2006 11:44, Steve [Gentoo] wrote: |
| 2 |
> Thanks for your help, and while it might not have been obvious to you |
| 3 |
> (or anyone else reading along)... everything that was confusing before |
| 4 |
> is clear now... to me at least. While I can see what is wrong, it isn't |
| 5 |
> 100% clear if it constitutes a bug or not. |
| 6 |
> |
| 7 |
> The problem is that the configure script starts '#!/bin/sh' - but goes |
| 8 |
> on to depend upon Bash specific features... specifically substitution. |
| 9 |
> I expect this would not be a problem for most users where /bin/sh is a |
| 10 |
> sym-link to /bin/bash.... but, for me, /bin/sh was a sym-link to |
| 11 |
> /bin/ash... and, for that shell, line 151 is invalid. |
| 12 |
|
| 13 |
Heh, I just hadn't noticed that the first line of the script said /bin/sh. |
| 14 |
That's definitely a bug. Either the script must be modified to only |
| 15 |
use /bin/sh features or it must request a shell that supports it... |
| 16 |
|
| 17 |
-- |
| 18 |
Bo Andresen |
Archives