-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 22 Oct 2002 07:57, David Dawes wrote: <snip of standard arguments about header files in Linux> > What is the correct way to handle headers that defined ioctls?
There simply is no good way. It is conceptually wrong to install a new kernel that doesn't have the same API to userspace, and not update the rest of the system (not just the development environment - you need to recompile every binary that touches the changed interface. The same applies to a dynamically linked library. If you change the interface to the library, then you need to update all the applications using it. The best work-around I can suggest is: 1. Assume that the headers you're working with (in /usr/include) match the installed glibc. 2. Assume that the kernel you're running on is the target. 3. Assume that the header files for that kernel can be found at /usr/src/linux/include 4. Assume that the user will help you if any of the above isn't true. This is where autoconf comes in handy, because you can test each feature, and deal with one problem at a time, and you can get fine-grained user hints. My personal solution is to use a source based distribution (in my case Gentoo, but others (eg any *BSD) probably offer similar advantages. When I change the kernel and am worried about an ABI change, I just rebuild the system. But it clearly won't work for everyone. Brad - -- http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9tHyhW6pHgIdAuOMRApzBAJ9MnI8qNVF0DhQIOYTBN0HQ0HPWQACgmnAv ZvvXtVMMWQKSPkD33ZYsPeI= =HKx1 -----END PGP SIGNATURE----- _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
