On 5/30/19 8:33 AM, Michael Orlitzky wrote:
>
> Is this something that can (should?) be fixed?
>
Ping, this should be reproducible. It's easy to work around, but is
extremely perplexing to its victims (I spent several hours debugging,
and I like to think I'm pretty good at this stuff) so I'd lik
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
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
