site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com You have to build your own xnu to get them. Because of this, they are considered SPI (System Private Interfaces). -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On May 22, 2007, at 11:47 AM, Thomas Inskip wrote: I am trying to build fs_usage on MacOS X 10.4.9, but it won't compile because some types, such as kbufinfo_t, kd_threadmap, and kd_buf. The included makefile sets the header search paths to / System/Library/Frameworks/System.framework/PrivateHeaders and / System/Library/Frameworks/System.framework/PrivateHeaders/bsd, which are not available with the standard Xcode distribution. Surprisingly the compiler does no complain about not being able to find any header files, so it must be finding the wrong ones elsewhere, presumably. Could someone please tell me where I can get System.framework/ PrivateHeaders? I have found past threads to this regard in the archives, but unfortunately no solutions. These header files describe the contract between the kernel and the code that you promise you will recompile each time you recompile the kernel, so that the data interfaces described by the structures and other data objects in those headers will match up between them. If the reason you are doing this is to use the code as the basis of your own tool, the normally suggested route is to write code to talk to the system supplied tool instead. This isolates your code from changes which could otherwise cause it to break, if you were to use the interfaces directly, yourself. This email sent to site_archiver@lists.apple.com