Hello, Stepan Kasal <[EMAIL PROTECTED]> writes: > but the generated scripts (configure and autotest) start with > #! /bin/sh > so they suppose they are executed by /bin/sh. > > If you want to use another shell for configure, you have to do > CONFIG_SHELL=/bin/ash /bin/ash ./configure > > So the question is how it happened that the script was started by another > shell then /bin/sh?
Well -- some stupid user (i.e. me) typed: `/bin/bash ./configure'. :-) Seems, like I got myself confused. Let me try to summarise: The user interface to `configure' defines that I should either use ./configure ... or CONFIG_SHELL=/my/favorite/shell /my/favorite/shell ./configure ... Trying /my/favorite/shell ./configure ... is not a proper use of configure and the behaviour of configure in such a case is (more or less) undefined. In other words, "Don't do that!" Bye, Ralf Menzel
