On Sat, Oct 04, 2003 at 07:50:20PM +0200, Jeroen Dekkers wrote: > > This is just too much of a burden for little gain. Everybody who uses > <linux/*> headers in general applications doesn't know what he is > doing. They will just #define USE_LINUX or whatever to get rid of the > warning/error. The real solution here is teaching people to do the > right thing, not putting silly things in glibc which don't solve the > problem at all.
Not if the error message is good an explanative. For example, it could point to a README in /usr/include/linux/README that explains why including Linux headers is generaly a bad idea, and why the USE_LINUX macro should not be used unless we really need to access kernel interfaces. There's a difference between people who don't know what they are doing, and people who are plainly dumbass idiots. If you tell them what's correct to do, most of them will learn what's correct to do. Anyway, the people fixing build errors after appliing this change are not likely the same that those who introduced the insanity in first place, so there's little chance that they arbitrarily define USE_LINUX. -- Robert Millan "[..] but the delight and pride of Aule is in the deed of making, and in the thing made, and neither in possession nor in his own mastery; wherefore he gives and hoards not, and is free from care, passing ever on to some new work." -- J.R.R.T, Ainulindale (Silmarillion) _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
