http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57699
--- Comment #5 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- Well, if a portable O/S like eCos would need such special treatment, the NO_IMPLICIT_EXTERN_C should not be bound to the target architecture, it would be far more appropriate to define the NO_IMPLICIT_EXTERN_C from the configure command line instead. Actually I would have expected that some fixinclude scripts should be able to fix this kind of coding errors in the header files. Are you sure we still need that kind of hack ?
