On Sat, Sep 5, 2020 at 4:18 PM Sidney Cadot wrote:
> (As an aside: I was surprised to see the number of processes that
> were started even when just doing a “./configure --help” (36 in all,
> including stuff like ‘rm', ‘mkdir', ‘chown’, and ‘ln’). To someone
> like me who is not familiar with the
Hi Zack,
> I'm curious how you came to notice it.
I’ve been running automated builds of several GNU packages under strace, to
gain an understanding of package interdependencies (i.e., which configure/make
scripts execute what commands). This popped up when I tried to automatically
parse the st
Thanks for reporting that. I just now rebuilt sed-4.8's 'configure' script with
Autoconf master (which advertises itself as version 2.69.301-14265) and the
problem seems to have been fixed there. We're planning Autoconf 2.70 for soon,
and the bug should be fixed once that comes out.
On Sat, Sep 5, 2020 at 7:51 AM Sidney Cadot wrote:
> When running ./configure (or even just ./configure --help), an execve()
> syscall is done to execute what seems to be a shell command.
>
> Usually the first argument to execve() is something like "/bin/sed" or
> "/usr/bin/gawk", but in this case
Hi all,
When running ./configure (or even just ./configure --help), an execve()
syscall is done to execute what seems to be a shell command.
Usually the first argument to execve() is something like "/bin/sed" or
"/usr/bin/gawk", but in this case it is:
"if test ${ZSH_VERSION+y} && (emulate sh) >
