Bug 746 - Building qemumips meta-toolchain-sdk failed
Summary: Building qemumips meta-toolchain-sdk failed
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided major
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 744
  Show dependency tree
 
Reported: 2011-02-20 21:46 UTC by Dexuan Cui
Modified: 2011-02-28 11:04 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dexuan Cui 2011-02-20 21:46:31 UTC
Some logs are:
http://autobuilder.pokylinux.org:8010/builders/nightly-external/builds/35/steps/shell_26/logs/stdio
http://autobuilder.pokylinux.org:8010/builders/nightly-external/builds/37/steps/shell_26/logs/stdio

ERROR: Error executing a python function in /srv/home/pokybuild/poky-slave/nightly-external/build/meta/recipes-core/eglibc/eglibc_2.12.bb:
CopyFailed: Command tar -cf - -C /srv/home/pokybuild/poky-slave/nightly-external/build/build/tmp/work/mips-poky-linux/eglibc-2.12-r13/sstate-install-package///package -ps . | tar -xf - -C /srv/home/pokybuild/poky-slave/nightly-external/build/build/tmp/work/mips-poky-linux/eglibc-2.12-r13/package failed with return value 2

The bug is there since Mark's commit 3e6d91ec, but the commit itself looks ok.

What's odd is: qemumips failed here while qemux86 and qemuarm are ok, and I can't reproduce the issue locally...

routerstationpro and atom-pc also have the same failure as qemumips.
Comment 1 Richard Purdie 2011-02-21 10:06:47 UTC
I have tracked down this problem to problems in tar versions less that 1.24. I've submitted some fixes to ensure we always have tar 1.25 available before extracting anything potentially with this problem (symlinks).
Comment 2 Dexuan Cui 2011-02-24 23:00:54 UTC
(In reply to comment #1)
> I have tracked down this problem to problems in tar versions less that 1.24.
> I've submitted some fixes to ensure we always have tar 1.25 available before
> extracting anything potentially with this problem (symlinks).

I don't meet with the bug now.