https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059
--- Comment #19 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #18) > You mean the #c14 comment 14 (< this adds a link) > change incorrectly adds > /tmp/tburnus-gcc-test/gcc/powerpc64le-linux-gnu/include-fixed > rather than > /tmp/tburnus-gcc-test/gcc/include-fixed/powerpc64le-linux-gnu > to search path? Maybe. Or rather: Yes, for the *being* *build* compiler (with "xgcc -B $BUILD/gcc") it *either* adds the wrong directory *or* fixinclude creates the wrong directory. However, for the *installed* compiler, we have: #include "..." search starts here: #include <...> search starts here: /tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include /usr/local/include /tmp/tburnus-gcc-test-inst/include /tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include-fixed/powerpc64le-linux-gnu /tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include-fixed /usr/include/powerpc64le-linux-gnu /usr/include End of search list. And as the fix-include floatn.h is under /tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include-fixed/powerpc64le-linux-gnu/bits/floatn.h
