Re: Kernel upgrade usr/src/linux
On Thu, Nov 24, 2005 at 10:18:50PM +0000, John Talbut wrote:
> Antony Gelberg wrote:
> >the user is meant to leave all management of /usr to dpkg, excluding
> /usr/local. Again, I have no reference to hand, although Martin Krafft
> mentions it in his book.
>
> Unfortunately I am stuck with a non-Debian module that makes calls to
> /usr/src/linux. I get the impression that this is likely to be fairly
> common for Debian users who need to use some non Debian software.
> Making /usr/src/linux a symlink seems to satisfy the "foreign" software
> without putting any files where they should not be.
Yes to "Fairly common *user* issue" :-)
> >If you feel the release notes are incomplete, then a bug report is
> probably the way to go (preferably with a patch)
>
> I have done so.
That did not work as I see.
I think the "software" you are talking is not binary but source file.
Then you are expected to do minimal changes before compiling.
Here is quote from somewhat outdated but still useful document called
"Debian Reference" which is meant to provide novice user with guide to
get used to Debian system after installation. Release note is not place
for this kind of contents.
------
7.1.3 Kernel headers
Most "normal" programs don't need kernel headers and in fact may break
if you use them directly; instead they should be compiled against the
headers with which glibc was built, which are the versions in
/usr/include/linux and /usr/include/asm of the Debian system.
So do not put symlinks to the directories in /usr/src/linux from
/usr/include/linux and /usr/include/asm, as suggested by some outdated
documents.
If you need particular kernel headers for some kernel-specific
application programs, alter the makefile(s) so that their include path
points to dir-of-particular-kernel-headers/include/linux and
dir-of-particular-kernel-headers/include/asm.
Cheers,
Osamu
Reply to: