[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What's Debian's /usr/src policy.


>>"Christoph" == Christoph Lameter <chris@waterf.org> writes:

Christoph> I want to be able to change the kernel-headers a program is
Christoph> compiled with. Certain tools (especially in 2.1.X) are
Christoph> dependant on a certain kernel version. Nothing wrong with
Christoph> providing the default as 2.0.33 f.e. (why 32??).

	Very few programs really need specific kernel headers. For the
 few that do, use -I/usr/src/kernel-headers-2.0.33. 

	libc development package need to include files found in
 kernel-sources to insulate most systems from the vagaries of bleeding
 edge kernel sources (you *do* need to include these header files,
 since one can't even include <errno.h> without having a valid

	There is a FAQ I seem to be posting continually arguing for
 not having libc development use any old (or new, or random) kernel
 headers; and libc5 did include a static set of kernel include files. 

	Unfortunately, the kernel header files are getting to be quite
 architecture dependent, and hence if libc development packages
 continued to include kernel headers explicitly, we would need
 different headers for different architectures, resulting in
 libc6-dev-i386, libc6-dev-m68k, et. al. 

	The current solution is to make the libc development package
 depend on one particular, stable, well tested, *supported* kernel
 headers, namely version 2.0.32, and let the kernel-headers package
 handle architecture dependancies (which it had to anyway).

	This is a working technical solution to having libc
 development package contain/depend on a well known static set of
 kernel headers (insulating the vast majority of programs that are not
 closely tied to kernel version specific internal data structures),
 while allowing the kernel headers to vary from architecture to
 architecture, and still allowing device driver authors from having
 any set of kernel headers they want on the machine through the simple
 artifice of adding a -I flag to the compilation flags.

	I think this solution works, and is an elegant solution. This
 report should be closed.

 who objects to purely aesthetic objections to excellent technical

 ps. email me if you need to see the argument on why libc development
      packages should depend on static set of debugged kernel headers.
 "May your future be limited only by your dreams." Christa McAuliffe
Manoj Srivastava  <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E

 "Infidels in all ages have battled for the rights of man, and have at
 all times been the fearless advocates of liberty and justice." Robert
 Green Ingersoll
Manoj Srivastava  <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: