Wine works around other problems on the build platform (eg. strength-reduce bug, detected a few lines after my patch in configure.ac). I don't see how broken headers are any different from a broken compiler or broken libraries, which we already detect and deal with in the configure script.
Mike
Dmitry Timoshkov wrote:
I.e. are you proposing to build a potentially broken Wine binaries instead of fixing a probable source of bug? Is there a point in turning warnings on if nobody pays attention to them or even tries to get rid of them if they annoy enough?