Follow-up Comment #1, sr#110612 (group autoconf): We regret the delay in responding to this bug report.
In principle, this is something we should try to fix, but I do not see a good way to do it. The problem is that there's no way (that I know of) to tell, when $0 is just "configure", whether the script was invoked with "sh configure" (in which case we should look _only_ in the current working directory when re-execing with a better shell) or with "configure" (in which case we should _not_ look in the current directory unless it appears in $PATH). Unless we can tell, any change would just be moving the problem around. (In case you didn't know, it is normal and fully supported to invoke a configure script that's not in the current working directory; the effect is to set things up to store the build output separately from the source tree. It's called a "split tree build". In fact, some projects _require_ you to build this way. That's why we can't just always look in the current directory.) If you or anyone else has ideas for how to tell "configure" from "sh configure", I am all ears. I would also happily take a patch to the documentation (probably install.texi is the place to put it) that tells people to use "sh path/to/configure" (whether or not "path/to" is ".") rather than "sh configure". _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/support/?110612> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/