[sr #110612] Re-exec of $as_myself chooses wrong configure script from PATH

[Michael Orlitzky]

Follow-up Comment #2, sr#110612 (group autoconf):

No problem. If I create,

$ cat configure 
#!/bin/sh
echo $0

in my home directory, then at least in bash and dash, the $PATH entry gets
prepended to $0 when it is needed to resolve "configure":

$ PATH=/home/mjo configure 
/home/mjo/configure
$ PATH=. configure 
./configure

Having tested on one platform and two shells, I conclude that there's no way
to get "configure" _without_ a directory separator, unless "sh configure" was
used :)

Alas, someone wrote that $as_myself code for a reason, so we're probably not
so lucky. I see the problem and if it's not fixable, that's OK. IIRC we only
wound up in this situation because someone created a tarball with a
non-executable configure script, and then the person writing the workaround
was unlucky and left out the "./". And then I was even more unlucky and had
both a shell without LINENO, and some other "configure" in my $PATH. It's not
worth spending a lot of time on.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110612>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/