https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109282
--- Comment #5 from Chris Johns <chrisj at rtems dot org> --- (In reply to Andrew Pinski from comment #4) > My bet if you do /bin/sh you would also get into trouble too ... I do not think it is /bin/sh but you are right with the link bring MacOS blocking an exe that should not run and it was related to my path and my mistake. Using make's $(SHELL) with an absolute path made the build ignore my broken set up and more robust. Make uses: build/libcc1/config.log:SHELL='/bin/sh' I think the path as a clean up is a good things to have.
