On Tue, Mar 12, 2002 at 11:33:38PM -0500, Gene Heskett wrote: > On Tuesday 12 March 2002 08:32 pm, Douglas Gilbert wrote: > >john meshkoff wrote:
[skip] > >John, > >The kernel compiles the sg driver (either built-in or a module) > >against the /<kernel_source_root>/include/scsi/sg.h header. > >It would be difficult (but not impossible) to get that file > >"out of sync" with the /<kernel_source_root>/drivers/scsi/sg.c > >file. I am the maintainer of those 2 files. > > > >SANE builds against /usr/include/scsi/sg.h which is maintained > >by the glibc people. Linux kernel source and glibc are > > distributed (almost) independently. Files such as sg.h are why > > "almost" is needed in the previous sentence :-) There is not > > much I can do about this contention other than point it out to > > people. > > > >Doug Gilbert > > Is there some 'carved in stone' rule that says he can't take the > sg.h from his kernel tree and put it in the usr/includes tree? > > ISTR I ran into a similar problem while trying to build something > (taper-6.9b maybe?) quite a ways back to the log, as in year+, > and wound up putting the kernel includes I needed right on top of > the ones that were being a problem child. IIRC it worked ok for > that compile, and I can't for the life of me recall whether I > ever undid that fix or not. I don't think I did, and between > then and the install of RH7.2 I built quite a few other things > from scratch. Hi, I seem to recall that older RedHat versions (or kernel versions, or both?) even had symlinks like /usr/include/linux -> /usr/src/linux/include/linux and /usr/include/asm -> /usr/src/linux/include/asm Older means here probably RH 4.x and kernel 1.2. So maybe it is still correct to use all kernel includes instead of the corresponding glibc includes. --Max Ushakov.