https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98318
--- Comment #6 from Nathan Sidwell <nathan at gcc dot gnu.org> --- FWIW my build server is CentOS Stream release 8 (x86_64), so it seems something's different in your setup. The toplevel make knows that libcody must be built before gcc. Perhaps the libcody build is failing, but not being reported? What happens if you cd into the libcody obj directory and try a 'make' there? (after you've hit the failure). What does that dir's config.log look like?
