> As for the technical issue, Roland is mostly but not entirely right > about what gnumach/include is for. > > It has both the interface files, and pseudo-clones of C library headers, > which don't get installed because the C library has better versions. In > that category are <sys/types.h>, <sys/time.h>, <sys/reboot.h>, > <sys/ioctl.h>, <mach/mig_support.h>, <mach/mach_traps.h>, > <mach/error.h>, and <alloca.h>, by my count.
Perhaps this seems a little opaque, so I'll describe the point: gnumach/include is, essentially, a special /usr/include for use by the kernel itself when compiling. It only should get things which belong in /usr/include. The reason for <alloca.h> and <sys/types.h> is because those are files found in /usr/include, even if on an actual installed system the versions in /usr/include are provided by a different package. thomas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
