jbra...@dismail.de, le mer. 25 oct. 2023 11:52:02 +0000, a ecrit: > October 25, 2023 3:43 AM, "Samuel Thibault" <samuel.thiba...@gnu.org> wrote: > > jbra...@dismail.de, le mer. 25 oct. 2023 03:40:16 +0000, a ecrit: > > > >> Or maybe GCC is partly at fault for the > >> Hurd's X86_64 building troubles? > > > > It's not at all. Nor is libtool. > > > > I occasionally had issues in ./configure, too. > > > > You'll say that's "yeah, it's all about auto-crap". No. > > > > It's *very* most probably about bash, simply. > > Hmmm. I guess in the long-term then, the bash issues should be fixed.
It'd really better be short-term, because currently we cannot really trust the built packages: what if due to shell script misbehavior ./configure misdetects features, forgets enabling some support etc. That'd lead to subtle incompatibilities that'll be hard to hunt down. > Could we change the default shell on X86_64 Debian Hurd in the meantime, > as a temporary solution? Don't take me wrong: I'm not saying the concern is *because* of bash, but *concerning* bash. Another shell could very well just face exactly the same concerns. And no, we cannot just switch it: libtool uses the bash features, so we have to fix the behavior of the system for bash (and /bin/sh already points to dash) Samuel
