> > > I think we should disallow direct inclusion of <linux/*.h> in Glibc, any
> > > comments?
> > 
> > This is not an issue related to the Hurd at all.  If you think that this
> > should be done, for whatever reason, you need to talk to the glibc
> > maintainers.
> 
> I know. But this seriously affects portability to non-Linux-based systems,
> which includes GNU/Hurd. 
> I'm really sick of encountering programs that break because of arbitrarily
> including <linux/*.h> stuff. Today I just recieved a patch for a program I
> maintain that adds an #include on <linux/limits.h> just to get the PATH_MAX
> macro. I'm going mad with this kind of stuff.
> 
> If people really want Linux-specific features, let them define _USE_LINUX or
> something like that.

Same problem for BSD porters. This is _really_ annoying for every
non-Linux porter/maintainer out there. I'd strongly support such
a move; perhaps starting with a deprecation #warn-ing, and later
changing this to a hard #error.

> Robert Millan

-- 
Farid Hajji. http://www.farid-hajji.net/address.html



_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd

Reply via email to