Hi,
I'm tracking the kernel by hand (following the git tree and doing some
hacking of my own). However whenever I try and emerge a ebuild that
involves a kernel module it usually fails to work out the correct
kernel:
* Determining the location of the kernel source code
* Found kernel source dir
On Wed, 25 Jan 2006 00:00:01 +, Alex Bennee wrote:
> There really is no need to force people to build as root under /usr/src
> so is it possible to educate portage to use the uname method to
> determine the root of the kernel tree for building kernel modules?
Portage doesn't build the modules
On 1/24/06, Alex Bennee <[EMAIL PROTECTED]> wrote:
> * If you are using KBUILD_OUTPUT, please set the environment var so
> that
> * it points to the necessary object directory so that it might
> find .config.
>
> However with all kernels you should be able to detrmine the root via
> uname -r:
>
Neil Bothwick <[EMAIL PROTECTED]> writes:
> On Wed, 25 Jan 2006 00:00:01 +, Alex Bennee wrote:
>
>> There really is no need to force people to build as root under /usr/src
>> so is it possible to educate portage to use the uname method to
>> determine the root of the kernel tree for building k
On Wed, 25 Jan 2006 16:05:21 +0100, Harald Arnesen wrote:
> > Portage doesn't build the modules in /usr/src, but it uses
> > the /usr/src/linux symlink to determine the kernel for which you wish
> > to build the modules; which may not be the same as returned by uname
> > -r.
> And that is a bug,
Alex Bennee wrote:
> Hi,
>
> However with all kernels you should be able to detrmine the root via
> uname -r:
>
> malory / # ls -l "/lib/modules/`uname -r`"
> total 212
> lrwxrwxrwx 1 root root31 Jan 15 17:16 build
> -> /home/alex/src/kernel/linux-2.6
> lrwxrwxrwx 1 root root31 Jan 15
6 matches
Mail list logo
