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 actually. The real bug here is that the configure.ac script of the package hardcodes POSIX_SHELL in the output while your reproducible builds effort treats this as a(n unsupported, at least in this scenario) cross compilation. The same issue would happen when you set CONFIG_SHELL=/bin/bash and then cross-compile xz-utils from GNU/Linux to, say, MirBSD, where There Is No Such Thing As /bin/bash. So the root of the problem is that xz-utils is not cross-compilable (well, not completely, and enough for Helmut’s bootstrapping effort). bye, //mirabilos -- Yay for having to rewrite other people's Bash scripts because bash suddenly stopped supporting the bash extensions they make use of -- Tonnerre Lombard in #nosec