https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125129
--- Comment #5 from Rainer Orth <ro at gcc dot gnu.org> --- I've found two other issues with the patch: * When I included it in a NetBSD/amd64 build, python3 wasn't found: there's only /usr/pkg/bin/python2.7 or /usr/pkg/bin/python3.13, no plain python3. As a result, the build failed with cp /vol/gcc/src/hg/master/testing/gcc/m2/target-independent/m2/gm2-libs.texi /var/gcc/regression/master/10.1-gcc-gas-gld/build/gcc/m2/gm2-libs.texi make[3]: *** No rule to make target '/var/gcc/regression/master/10.1-gcc-gas-gld/build/gcc/m2/gm2-libs-iso/SYSTEM.def', needed by 'SYSTEM-iso.texi-check'. Stop . make[3]: *** Waiting for unfinished jobs.... echo timestamp > gm2-libs.texi-check * Another issue occured in a Solaris/SPARC bootstrap: at some point the build hang with two python processes: 18687: python3 /vol/gcc/src/hg/master/local/gcc/m2/tools-src/def2doc.py -t -b/var/gcc/ argv[0]: python3 argv[1]: /vol/gcc/src/hg/master/local/gcc/m2/tools-src/def2doc.py argv[2]: -t argv[3]: -b/var/gcc/regression/master/11.4-gcc/build/gcc/m2 argv[4]: -f/var/gcc/regression/master/11.4-gcc/build/gcc/m2/gm2-libs/SYSTEM.def argv[5]: -o argv[6]: /var/gcc/regression/master/11.4-gcc/build/gcc/m2/SYSTEM-pim.texi Both were in loops trying to read from fd 4 (unfortunately I forgot to check what that was): the 8 kB reads only returned 0, but the process kept trying...
