[yocto] build failure on current

[Paul Eggleton]

On Friday 28 September 2012 11:53:53 Evade Flow wrote:
> > > Erm... that *specific* bit prints nothing when pasted into a file and
> > > executed. (Is it really supposed to?)
> > 
> > No, but the rest of the script (the bit following the blank line that
> > you've omitted) is...
> 
> My bad, sorry. (I really need to read more carefully.) Here's what I get
> when I add the missing lines:
> 
> evadeflow% cat > temp.sh
> #!/bin/sh
> needtar=1
> TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
> float_test() {
>      echo | awk 'END { exit ( !( '"$1"')); }'
> }
> 
> # Tar version 1.24 and onwards handle overwriting symlinks correctly
> # but earlier versions do not; this needs to work properly for sstate
> float_test "$TARVERSION > 1.23" && needtar="0"
> echo $needtar
> evadeflow% chmod +x temp.sh
> evadeflow% ./temp.sh
> 1
> 
> So... it correctly determines that it needs to build tar, but... the built
> tar can't unpack the tarball from CPAN:
> 
> evadeflow% wget http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
> --2012-09-28 11:46:13--  http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
> Resolving usaprox1.lightning.com... 10.102.184.7
> Connecting to usaprox1.lightning.com|10.102.184.7|:8080... connected.
> Proxy request sent, awaiting response... 200 OK
> Length: 15223598 (15M) [application/x-gzip]
> Saving to: `perl-5.14.2.tar.gz'
> 
> 100%[================================================================>]
> 15,223,598  62.2M/s   in 0.2s
> 
> 2012-09-28 11:46:13 (62.2 MB/s) - `perl-5.14.2.tar.gz' saved
> [15223598/15223598]
> 
> evadeflow% ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar xf
> perl-5.14.2.tar.gz
> 
> gzip: stdin: invalid compressed data--crc error
> ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Child returned status
> 1 ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Error is not
> recoverable: exiting now
> 
> 
> Weird. Anyway, I have a workaround, so it's not a big deal--especially given
> that Ubuntu 10.04 isn't officially supported.  I'm happy to run any other
> tests you can think of to hunt down the cause of this (I've got a pretty
> fast build mchine now), but I totally understand if you've got bigger fish
> to fry at the moment...

Is it definitely tar that's the problem or gzip? This would suggest gzip:

http://code.google.com/p/go/issues/detail?id=3443

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre