On Sun, Nov 23, 2008 at 05:49:14PM -0600, Manoj Srivastava wrote:
> On Sun, Nov 23 2008, Frans Pop wrote:

> > Daily builds of D-I for sparc have been failing with:
> > gzip: ./tmp/netboot/vmlinuz-2.6.26-1-sparc64: not in gzip format
> 
>         The only thing I can see is that sparc processing in k-p defines
>  NEED_DIRECT_GZIP_IMAGE.  Now, what kernel-package thinks is the
>  architecture is taken from either
>   a) user specified value,
>   b) dpkg-architecture  -qDEB_HOST_ARCH_CPU
> 
>         If the architecture contains the string sparc, then we arrange
>  to gzip the image. If this is not happening, we need to determine if it
>  tried to compress, but compressed the wong file, or it did not try to
>  compress it at all, or if the actual image is in some other place.
> 
>         If the build logs for the kernel image show which of these
>  scenarios it is, it can be easily fixed. So the build log of the kernel
>  image would be useful.

The latest log is at 

 
http://buildd.debian.org/fetch.cgi?pkg=linux-2.6;ver=2.6.26-10;arch=sparc;stamp=1226181471

but beware; it contains binary data not well handled by (at least my)
iceweasel.

It's easy to see what goes wrong:

 gzip -9vc 
/build/buildd/linux-2.6-2.6.26/debian/build/build_sparc_vserver_sparc64/debian/linux-image-2.6.26-1-vserver-sparc64//boot/vmlinuz-2.6.26-1-vserver-sparc64
 
/build/buildd/linux-2.6-2.6.26/debian/build/build_sparc_vserver_sparc64/debian/linux-image-2.6.26-1-vserver-sparc64//boot/vmlinuz-2.6.26-1-vserver-sparc64:
     ^_&#824<
 [...]

The gzip invocation uses -c (--stdout) without a target.

This comes from kernel/ruleset/targets/image.mk in the kernel-package source,
and git-blame gives

commit e12e61540e1b904253dcec1b781e1e58e1e0728a
Author: Manoj Srivastava <[EMAIL PROTECTED]>
Date:   Thu Oct 9 20:43:11 2008 -0500

    Fix the build system to accommodate XEN changes, use kbuild as far as 
possible
    
so the bug was apparently introduced in 11.003.
-- 
Niko Tyni   [EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to