https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90379
--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Marius Maraloi from comment #2) > (In reply to Richard Biener from comment #1) > > You need to do 'make -k check' since some tests are always expected to fail. > I ran 'make -k check', it produces the same result as without '-k': 'make -k check' will not alter that the fixincludes test fails, but it will allow the check process to continue with testing other parts of the toolchain (and is generally required as Richi says, since testing is expect to contain some, small number, of fails usually).
