<sys/file.h> issue

[kaliber]

Some applications uses a <sys/file.h> (our jam also includes this file). BeOS (at least MAX distribution) also have <sys/file.h>.

Maybe we should have such file in Haiku?

[kaliber]

Try svn log headers/glibc/_G_config.h

hrev14109 | bonefish | 2005-09-03 23:44:38 +0000 (Sat, 03 Sep 2005) | 27 lines

....

• Added a headers/posix/sys/file.h. There was one in BeOS and some code was including it.

[axeld]

It's a non-standard header (in terms of open standards, not actual practice), so I've removed it a while back. We might want to put it into some legacy header directory, I dunno. It's the usual balance between fixing apps that unconditionally use it, and giving you a more satisfying porting experience :-) Opinions are welcome.

[korli]

Legacy header directory seem like the logical place.

[kaliber]

Replying to korli:

Legacy header directory seem like the logical place.

I agree, but legacy/ directory should be visible by GCC? If not, this doesn't change anything, because every app that use <sys/file.h> should be fixed.

[korli]

Added in hrev23836.

[aljen]

about legacy dir, we could add this line { "/boot/develop/headers/be/legacy", 0, 0, 0 },\ to INCLUDE_DEFAULTS in #ifndef CROSS_COMPILE and this line { CROSS_INCLUDE_DIR "/be/legacy", 0, 0, 0 },\ to INCLUDE DEFAULTS in #else of that ifdef in buildtools/gcc/gcc/config/haiku.h, now gcc should see legacy dir