------- Comment #19 from martin dot jansa at mk dot cvut dot cz 2007-03-12 22:30 ------- (In reply to comment #18) > (In reply to comment #17) > > I can confirm this patch works on an amd64 gentoo sytem too. > > And what happens if you just change that #include_next to #include <stdio.h>, > that would be useful in understanding the issue and how much of it has to do > with #include_next (note that, at the moment, as far as I can see, the > #include_next special features are still not used)
this isn't enough even with building with this brand new gcc-4.3.0_alpha20070309. I'll repeat it with include of proper stdio.h, which looks in gentoo multilib like this jama gcc # cat /usr/include/stdio.h /* Autogenerated by create_ml_includes() in multilib.eclass */ #ifdef __i386__ # include <gentoo-multilib/x86/stdio.h> #endif /* __i386__ */ #ifdef __x86_64__ # include <gentoo-multilib/amd64/stdio.h> #endif /* __x86_64__ */ and with #include <stdio> without ".h" after that so I'll send results tomorrow -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30915
