Because if you chroot into your dev setup then you will have _no_ access to the desktop machine's files etc (from within the chroot) and therfore emerging inside the chroot can not use linux source outside the chroot. You must be either doing something wrong or doing this in a way very different from how I would.
Ahmed.
On 26/06/06, Joshua ChaitinPollak <[EMAIL PROTECTED]> wrote:
I'm trying to emerge the madwifi-ng module into my embedded system's
dev environment, but the ebuild is trying compile against the kernel
version installed on my desktop, not the version installed in the
chrooted development environment. Is there a way to force external
module ebuilds to use a specific kernel version?
Thanks,
-Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
--
[email protected] mailing list
