------- Comment #9 from david dot kirkby at onetel dot net 2010-01-15 18:25 ------- (In reply to comment #8) > Fixincludes is part of the compiler sources, and it is the part that should > work around GCC-incompatible system headers (such as this one) by making > fixed copies when GCC is built and installed. Thus, a failure to fix it > indicates a limitation in fixincludes, and the fix would be to enhance > fixincludes and rebuild GCC. > > It is not part of the C front end, so "c" is not the correct component. Do > not change components back if a maintainer changes them to be more accurate.
Is this is trivial fix that could be implemted quickly, or it will require quite a bit of work, and so I should not expect a solution soon? Is there any workaround you can suggest? Would simply adding #define _Complex_I _Complex_I #define complex _Complex #define _Imaginary_I _Imaginary_I #define imaginary _Imaginary #undef I #define I _Imaginary_I at the top of the source files work? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42753
