Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#1332 closed bug (fixed)

<sys/file.h> issue

Reported by: kaliber Owned by: axeld
Priority: normal Milestone: R1
Component: - General Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All


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?

Change History (6)

comment:1 by kaliber, 13 years ago

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.

comment:2 by axeld, 13 years ago

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.

comment:3 by korli, 13 years ago

Legacy header directory seem like the logical place.

in reply to:  3 comment:4 by kaliber, 13 years ago

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.

comment:5 by korli, 12 years ago

Resolution: fixed
Status: newclosed

Added in hrev23836.

comment:6 by aljen, 12 years ago

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

Note: See TracTickets for help on using tickets.