Ximin Luo dixit:
>needs to more clearly distinguish between the build and the host
>environment - like how compilers do. So for example, here the "most
>correct" solution would be to add a HOST_POSIX_SHELL and default this
No, this is outside of the scope of autotools and a common misuse
of them
Ximin Luo dixit:
>(Did you mean to add debian-bugs-dist and Jonathan Nieder on purpose
>or by accident? I removed them, but feel free to add them back in.)
I didn’t, maybe debbugs did.
>In other words: in your scenario, one would not use $POSIX_SHELL but
>some other specific test for those
Paul Eggert:
> On 06/15/2016 01:44 PM, Ximin Luo wrote:
>> In such a case, it is a bug to be using $POSIX_SHELL - which only tests for
>> conformance with POSIX and not these "other bugs that make it unusable".
> Gnulib can't test for all POSIX violations, only for the ones it knows about.
>
Ximin Luo dixit:
>I'm not sure if you understood what was being discussed.
I understand it extremely well.
>proposed patch affect your scenario? This is not about CONFIG_SHELL,
It is. Straight from your diff:
> for gl_cv_posix_shell in \
>-"$CONFIG_SHELL" "$SHELL" /bin/sh
+bugs-gnulib, reproducible-builds
Lasse Collin:
> On 2016-06-07 Ximin Luo wrote:
>> I've attached a patch that makes m4/posix-shell.m4 try constant paths
>> first. This should fix the issue.
>>
>> Upstream should also apply it - see more-stable-shell.patch.
>
> Thanks!
>
> posix-shell.m4 comes
