On Wed, 08 Nov 2006 10:44:31 +0000, Steve [Gentoo] wrote: > 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. What is less > clear is whether or not, in a Gentoo context, it is 'correct' to have > /bin/sh being Borne-like but not Bash-like. By preference I'd prefer > /bin/sh to be the minimal shell that will execute Borne-shell scripts... > but I recognise the Linux-world normality of /bin/sh actually being > bash.
Bash behaves differently when called as sh, to avoid just this sort of problem. However, if the script calls /bin/sh while requiring bash features it is clearly broken and a bug should be files. Unfortunately, this type of breakage is all too common; I tried using dash as /bin/sh for a short while and found all sorts of things falling over. In this case, it can be easily fixed, by the ebuild altering the shebang line of configure before running it. -- Neil Bothwick Psychiatrists say that 1 of 4 people are mentally ill.
signature.asc
Description: PGP signature
