Modernizing Fedora's C code

1. I said "wrap for". The point being, if you want to just find 'configure' or configure-ish failures, and avoid this affecting package builds (which makes things awkward because you then can build things which depend on it), it can be a problem. We do sandbox builds including network but yes, it'll be doable to store in a file somewhere.

2/3. Right, it's a good idea. You indeed don't have to worry about diffing later, you can import if something simply doesn't compile with the second compiler. I'll go play with it.

4. It's really just the nature of the large amount of software out there. Some of these bugs will end up hitting other distros anyway.

5. Yes, it is, because you have to go around running autoreconf in tonnes of packages when the configure scripts in the release tarball are stale (and it's not fixed in an autoconf release, so new releases of software will continue to be broken).

Would it perhaps have been more acceptable to you if I'd said "complex" rather than "hard", as there's many factors? :)