On 07/19/2011 10:15 PM, Cody A.W. Somerville wrote:
> Please accept this patch which will append 'linux32' to LB_ROOT_COMMAND
> if 'uname -m' is x86_64 and LB_ARCHITECTURE is i386.
appart from the typo ('&' instead of '&&'), this should
Hello,
Please accept this patch which will append 'linux32' to LB_ROOT_COMMAND if
'uname -m' is x86_64 and LB_ARCHITECTURE is i386. This fixes build failures
due to dkms module makefiles relying on uname -m to determine which linux
kernel headers to use.
Cheers,
--
Daniel Baumann wrote:
just for making sure you're not potentially wasting time: that driver is
included in linux mainline. if you are building a lenny image and
requiring a newer kernel in order to get a newer version of the driver
for your hardware, but you're not depending on bleeding edge, you
Tom Deblauwe wrote:
>> fix whatever you are compiling to not rely on uname -r, but use KVERS or
>> similar (which can be set by the user).
>
> I would rather not do this if possible.
well, if the driver is sane, it does this already correctly through the
kbuild stuff and
Daniel Baumann wrote:
fix whatever you are compiling to not rely on uname -r, but use KVERS or
similar (which can be set by the user).
I would rather not do this if possible.
it would be handy to know what you're exactely compiling, that way we
could tell you if you're doing i
Tom Deblauwe wrote:
> Hello,
Hi,
> if I want to use another version for my
> live-system, the result of the command "uname -r" in the chroot gives me
> the host kernel version, and the compile fails. Is there a solution for
> this?
fix whatever you are compiling to not
r my
live-system, the result of the command "uname -r" in the chroot gives me
the host kernel version, and the compile fails. Is there a solution for
this?
Thanks a lot,
Best regards,
Tom,
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsub
