Both the Windows build and the Linux build fail with the following problem: :
2019-12-02T14:13:00.4734142Z configure: error: computing EOF failed
2019-12-02T14:13:00.5213975Z checking for the value of EOF... Makefile:11514: recipe for target 'configure-target-libstdc++-v3' failed
2019-12-02T14:13:00.5221295Z make: *** [configure-target-libstdc++-v3] Error 1
2019-12-02T14:13:00.5221579Z FAILED COMMAND: make $PARALLEL_MAKE all-target-libstdc++-v3
2019-12-02T14:13:00.5229503Z ##[error]Process completed with exit code 2.
2019-12-02T14:13:00.5254617Z Cleaning up orphan processes
Interestingly, if I remember correctly I was able to replicate the problem if I launched a bash with /bin/bash --noprofile --norc -e -o pipefail, exactly how the GitHub Actions does. However, the problem dues to some strange interaction between bash and the autotools-based build system of GCC . As we seldom update the compiler, I think for now it is ok to build manually the compiler. If we ever need to automatize this process, a possible choice could be to use a private GitHub Action runner.
Both the Windows build and the Linux build fail with the following problem: :
Interestingly, if I remember correctly I was able to replicate the problem if I launched a bash with
/bin/bash --noprofile --norc -e -o pipefail, exactly how the GitHub Actions does. However, the problem dues to some strange interaction between bash and the autotools-based build system of GCC . As we seldom update the compiler, I think for now it is ok to build manually the compiler. If we ever need to automatize this process, a possible choice could be to use a private GitHub Action runner.