Eric Blake wrote: > Can anyone think of a way to detect broken system > headers that were relying on 'extern inline', in such a way that we can make > the gnulib wrapper headers nuke those troublesome declarations out of the > headers?
[1] contains a test case. How to modify the glibc headers, see the patch that was committed into the glibc CVS on 2007-03-16. > Are we stuck with just > telling these users that they shouldn't upgrade gcc without also upgrading > their headers, because the old headers are broken with the new gcc? The traditional place to handle situations like this is gcc's 'fixincludes'. It's better than putting a workaround into gnulib, because it fixes the problem for all C source code. Unfortunately this issue appears to be low-priority to the gcc developers. Bruno [1] http://sourceware.org/bugzilla/show_bug.cgi?id=4022
