https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105144
--- Comment #10 from Khem Raj <raj.khem at gmail dot com> --- (In reply to Andrew Pinski from comment #9) > (In reply to Andrew Pinski from comment #8) > > (In reply to Khem Raj from comment #7) > > > in Yocto we build outside the source tree. And during cross-build it will > > > copy aarch64.h into builddir and use it from there but then build can not > > > find files it includes since its being included from builddir. This patch > > > below helps > > > > aarch64.h is never copied into the builddir. > > Even for cross builds. > I think something else is wrong. Please file a different bug with the full > log? Including the part where the copy happens because I just did a: > find . -name aarch64.h > in the build directory of the cross build of GCC 12 I had around and there > was no such file happening. you are right. I should have mentioned that these copying is done by yocto builds for working though its notion of multilibs [1]. However, I think if we apply this fix it should not regress builds and we will have one less patch to carry in yocto. [1] https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/gcc/gcc-multilib-config.inc#n30
