On Sat, 2004-06-12 at 06:48, Pablo Santiago Blum de Aguiar wrote:

> I compiled a new kernel (2.4.18) for a woody box (a 233MHz pc) on my sid
> box (an Athlon 800MHz pc). On sid, I did an 'apt-get install
> kernel-source-2.4.26', configured the kernel for my needs, ran
> 'make-kpkg clean' and used the following command do compile it:
> 
> [/usr/src/linux] - 0
> [EMAIL PROTECTED] # MAKEFLAGS="CC=gcc-2.95" make-kpkg \
> > --append_to_version  -586mmx --revision=rev.01 \
> > --initrd kernel_image modules_image
> 
> what gives me a 2.9M file kernel-image-2.4.18-586mmx_rev.02_i386.deb. It
> makes me to think that I have a sucessful compiled kernel.
> 
> Ok, but when trying to install the image on the woody box this is what I
> get:
> 
> [~/kernel] - 0
> [EMAIL PROTECTED] # dpkg --configure kernel-image-2.4.18-586mmx
> dpkg: dependency problems prevent configuration of
> kernel-image-2.4.18-586mmx:
>  kernel-image-2.4.18-586mmx depends on initrd-tools (>= 0.1.48);
> however:
>   Version of initrd-tools on system is 0.1.32woody.3.
> dpkg: error processing kernel-image-2.4.18-586mmx (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  kernel-image-2.4.18-586mmx

If you want to use initrd then the best thing is probably to use a
chroot of woody on your sid box.
It shouldn't need much diskspace and ensures you use the same tools as
if you were doing it on a woody box (I do this for my woody box so I
don't have to have compilers on a server).

dchroot is the package you want. I can't remember how I set up the
chroot, but it is documented.

HTH
Tristan

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to