On Wed Dec 28 20:55:11 2011
Sean McGovern wrote:
> The check_exec_crash function is supposed to run the test in a subshell so
> that the SIGTERM that it raises does not cause 'configure' itself to
> terminate, only the subshell it was executing inside. I'm not certain how
> to test /usr/xpg4/bin/sh to see if it is actually properly spawning a
> subshell though. Perhaps with truss(1) somehow?
>
> As this seems to be the only POSIX shell it fails on (that we are aware of
> anyways), maybe this isn't worth pursuing any further? I've already set the
> /bin/sh wrapper to spawn /bin/bash instead.
You should not need a wrapper to run configure, hack fate.sh.
${sh} ${src}/configure will run configure using a shell from your config,
it could be any POSIX-compliant shell, not just the slowest one.
Michael
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
