On Thu, 20 Jan 2005 05:05:07 +0100, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
> >There is no kernel-image-2.4.27-r5k-cobalt source. The mipsel cobalt kernels >are built from the kernel-patch-2.4.27-mips source package. The 2.4-cobalt >patch is only for i386 cobalts like RaQ3. hi actually I'm not so sure here... If I do the following: apt-get source kernel-image-2.4.27-r5k-cobalt I pretty much get the "kernel-patch-2.4.27-mips-2.4.27-7.040815" in /usr/src :) (including .dsc and .tar.gz) implicitely "dpkg-source -x kernel-patch-2.4.27-mips_2.4.27-7.040815-1.dsc" is done by apt-get then. well I do cd /usr/src/kernel-patch-2.4.27-mips-2.4.27-7.040815/ and try to "dpkg-buildpackage" this is where it tells me about the 2.4.27-7 requirement, which I filled in trying to sole this by apt-getting it form /unstable. afterwards "make-kpkg clean" during the above buildpackage call complains about not having "kimagesrc" set and bails out, I tried to set ARCH SUBARCH KPKG_SUBARCH KPKG_ARCH to mipsel and r5k-cobalt, but still "make-kpkg clean" is pretty unhappy about it and tells me kimagesrc is probably missing because it can't determine the arch/subarch... >> now - my stupid question: how comes the patch is in testing for cobalt, but >> the >> source-tree is not yet available - does this make any sense? > >kernel-patch-2.4.27-mips Build-Depends on kernel-source-2.4.27. The >testing migration scripts care about Depends, not Build-Depends. uhm - I'm a non-guru here - if you could explain this a bit more to me please? (or send me to rtfm :)) >> and more interesting: is there a workaround for me to build my own kernel >> anyway? > >Use kernel-patch-2.4.27-mips plus the kernel-source-2.4.27 deb from unstable. that's what I'm doing as described above I hope, but somewhere on the way I still get stuck with dpkg-buildpackage. thank you for your support harald kapper
