https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104290
--- Comment #8 from Svante Signell <svante.signell at gmail dot com> --- > If you make all-target-libgo all dependencies are respected. Sorry but that is not how things work: all-target-libgo: maybe-all-target-libffi is outside any conditionals, but all-target-libgo: maybe-all-target-libbacktrace all-target-libgo: maybe-all-target-libatomic are inside the conditional @unless gcc-bootstrap @endunless gcc-bootstrap in src/Makefile.in :( and therefore not included in the generated build/Makefile. The unless/endunless condition does not seem to be met in the generated build/Makefile. As far as I've searched, no understandable explanation of @unless/@endunless gcc-bootstrap is found in the gcc-12 tree either. No explanation in Makefile.tpl I found only a commit for binutils-gdb: https://isrc.iscas.ac.cn/gitlab/mirrors/sourceware.org/git_binutils-gdb/-/commit/4119873a48042e532f7485b84cca83ea0bf1fcf6 but that one is not very informative :( moving all-target-libgo: maybe-all-target-libbacktrace all-target-libgo: maybe-all-target-libatomic next to all-target-libgo: maybe-all-target-libffi in Makefile.in all works fine. Generating a new version of Makefile.in by: (cd source; autogen Makefile.def) does not solve the problem: the same buggy build/Makefile is created. This is not a Debian problem, it is an upstream bug, as far as I've found. It seems like everything not linux-any is left unsupported, not a nice situation... Your choice! And patching gnu.h to not support split-stack any longer is really not nice. Don't you ever build gcc for GNU/Hurd? If not maybe I can help to set up such a build environment. Just let me know!! Thanks!
