Re-exec of $as_myself chooses wrong configure script from PATH

In the configure scripts that I'm generating, I see the following variable assignment: # Find who we are. Look in the path if we contain no directory # separator. as_myself=... Later, this may be used to re-exec the configure script with a better shell, exec $CONFIG_SHELL $as_opts "$as_

Re: Re-exec of $as_myself chooses wrong configure script from PATH

On 5/30/19 7:33 AM, Michael Orlitzky wrote: > In the configure scripts that I'm generating, I see the following > variable assignment: > > # Find who we are. Look in the path if we contain no directory > # separator. > as_myself=... > > Later, this may be used to re-exec the configure scri

Re: Re-exec of $as_myself chooses wrong configure script from PATH

On 5/30/19 9:39 AM, Eric Blake wrote: > > Executing 'sh configure' should execute whatever 'configure' is first on > your PATH, which is not ./configure unless '.' is early in your PATH. Are you sure about this? I wouldn't swear to it, but a quick check of POSIX suggests that it should run ./conf