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

2023-12-08 Thread Zack Weinberg
Update of sr#110612 (group autoconf): Status:None => Need Info ___ Follow-up Comment #4: This is all helpful but I'm leaving this marked "need info" until someone has the time to do a

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

2023-12-07 Thread Paul Eggert
Follow-up Comment #3, sr#110612 (group autoconf): [comment #1 comment #1:] > If you or anyone else has ideas for how to tell "configure" from "sh configure", I am all ears. If it's Bash, "$_" (at the start of the script) should tell you. This is true for other shells (e.g., it works with

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

2023-12-07 Thread 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 $

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

2023-12-07 Thread Zack Weinberg
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

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

2022-02-18 Thread Michael Orlitzky
URL: Summary: Re-exec of $as_myself chooses wrong configure script from PATH Project: Autoconf Submitted by: mjo Submitted on: Sat 19 Feb 2022 01:07:39 AM UTC Category: None