[Bug other/91085] fixincludes breaks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91085 --- Comment #14 from Bruce Korb --- Reworking fixfixes.c seems pretty heavy duty. I'm downloading the GCC sources now. I'll take a peek tomorrow.
[Bug other/91085] fixincludes breaks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91085 --- Comment #15 from Bruce Korb --- Obviously, "print_quote()" was needed early on (1999) and then saved for prosperity :). Your patch is inadequate because it will have to not expand 'linux' in a line such as: #if __has_include() In other words, it will have to skip over three flavors of quote. Or just two, if you omit apostrophe quotes. In any event, the '<' character will have to be matched with '>', which is a tiny change to the logic. Don't forget to add tests in the final result.
[Bug target/93082] macOS Authorization.h needs fixinclude
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082 --- Comment #8 from Bruce Korb --- It should not be terribly difficult to add another include tree for fixinc to search. Also, unless 32 is cast as forever being the only value kAuthorizationExternalFormLength could possibly ever have: select= "static const size_t kAuthorizationExternalFormLength = (32);\n"; c_fix = format; c_fix_arg = "enum { kAuthorizationExternalFormLength = %1 };\n"; BTW: 1. if you're going to simply replace text 2. on page https://gcc.gnu.org/wiki/GitMirror the "getting started" section leads to this error: > fatal: 'svn/trunk' is not a commit and a branch 'trunk' cannot be created > from it (I don't have access to the GCC tree anymore [lost keys], so I'm starting over.)
[Bug target/93082] macOS Authorization.h needs fixinclude
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082 --- Comment #9 from Bruce Korb --- Um, I didn't finish my misthink for item#1 above. Please ignore. :)
[Bug target/105719] RFE: fixincludes should handle Frameworks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719 --- Comment #5 from Bruce Korb --- 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. :)