https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719
--- Comment #5 from Bruce Korb <bkorb at gnu dot org> --- It's been a long time since I mucked with fixincludes. My first guess, without going back and reading code, would be to provide fixincludes with a list of trees to traverse and not have it burned into fixincludes at all. That might even be helpful for cross compiles also. :)
