Re: [gentoo-dev] Ebuilds referencing /usr/src/linux makes baby Jesus kill kittens

["Donnie Berkholz" <spyderous@gentoo.org>]

Ciaran McCreesh said:
> Just a friendly reminder that you should really avoid messing around
> with /usr/src/linux inside ebuilds. In particular, code like the
> following is utterly wrong:
<snip>
> Don't try to do clever things with /usr/src/linux to determine whether a
> kernel has a particular feature. Especially don't go near .config. The
> kernel running may not be the kernel in /usr/src/linux. The box in
> question might be a chroot setup or a netboot system or a system built
> with a crosscompiler, in which case /usr/src/linux* won't exist at all.
> The user might be sharing kernel binaries between dozens of identical
> boxes and only building on one. The user might be building kernels
> in/home to avoid having to build kernels as root or chown a bunch of
> stuff. The /usr/src/linux symlink might be out of date. The box might be
> building binary packages for a different system.

Just a friendly response that kernel modules should build based on
${ROOT}/usr/src/linux and not on the running kernel. Also other things
that require a kernel should be using that symlink rather than the running
kernel. That's how it's been in Gentoo in the past. The rationale is the
ability to build things for a (or multiple) non-running kernel(s).

The FAQ to which you refer only talks about not using the symlink for your
headers, which is an entirely different thing from what I'm getting at.

Donnie



--
gentoo-dev@gentoo.org mailing list