https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I wonder how it works for Tobias then.
If the fixincluded headers go to
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/powerpc64le-linux-gnu/bits/floatn{,-common}.h
and search path is:
...
/home/seurer/gcc/git/build/gcc-test/./gcc/include
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed
/usr/local/include
/usr/include/powerpc64le-linux-gnu
/usr/include
then I think it can't find those headers for #include <bits/floatn.h>
Given the above, I think the search paths should be:
...
/home/seurer/gcc/git/build/gcc-test/./gcc/include
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/powerpc64le-linux-gnu
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed
/usr/local/include
/usr/include/powerpc64le-linux-gnu
/usr/include
because the multiarch subdir sits below /usr/include and so is fixincluded
together with it. I'd be afraid we fixinclude all the other arches if they
are, so if one has
/usr/include/powerpc64le-linux-gnu/bits/floatn.h
/usr/include/x86_64-linux-gnu/bits/floatn.h
both would go to:
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/powerpc64le-linux-gnu/bits/floatn.h
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/x86_64-linux-gnu/bits/floatn.h
so making fixincludes itself multiarch aware is going to be difficult.
