| 1 |
I am building the module inside the chrooted environment. It seems |
| 2 |
that the kernel module ebuild's use uname to figure out which kernel |
| 3 |
version to compile against, because my desktop is running 2.6.15- |
| 4 |
gentoo-r2 and the ebuild fails with "/lib/modules/2.6.15-gentoo-r2/ |
| 5 |
build is missing" I just now realized the error also says "Please set |
| 6 |
KERNELPATH", so I'm going to try setting that and see if it helps. |
| 7 |
|
| 8 |
-Josh |
| 9 |
|
| 10 |
On Jun 26, 2006, at 1:40 PM, Ahmed Ammar wrote: |
| 11 |
|
| 12 |
> Sorry how did you build your kernel ? Did you not build it inside |
| 13 |
> the same chroot ? and is it in ($chroot)/usr/src/linux ? |
| 14 |
> |
| 15 |
> Because if you chroot into your dev setup then you will have _no_ |
| 16 |
> access to the desktop machine's files etc (from within the chroot) |
| 17 |
> and therfore emerging inside the chroot can not use linux source |
| 18 |
> outside the chroot. You must be either doing something wrong or |
| 19 |
> doing this in a way very different from how I would. |
| 20 |
> |
| 21 |
> Ahmed. |
| 22 |
> |
| 23 |
> On 26/06/06, Joshua ChaitinPollak <jpollak@×××××××××××.com> wrote: |
| 24 |
> I'm trying to emerge the madwifi-ng module into my embedded system's |
| 25 |
> dev environment, but the ebuild is trying compile against the kernel |
| 26 |
> version installed on my desktop, not the version installed in the |
| 27 |
> chrooted development environment. Is there a way to force external |
| 28 |
> module ebuilds to use a specific kernel version? |
| 29 |
> |
| 30 |
> Thanks, |
| 31 |
> |
| 32 |
> -Josh |
| 33 |
> |
| 34 |
> -- |
| 35 |
> Joshua ChaitinPollak |
| 36 |
> Software Engineer |
| 37 |
> Kiva Systems |
| 38 |
> |
| 39 |
> |
| 40 |
> -- |
| 41 |
> gentoo-embedded@g.o mailing list |
| 42 |
> |
| 43 |
> |
| 44 |
|
| 45 |
-- |
| 46 |
Joshua ChaitinPollak |
| 47 |
Software Engineer |
| 48 |
Kiva Systems |
Archives