From: wenzong fan <wenzong.fan@windriver.com>
To: "'Patches and discussions about the oe-core layer'"
<openembedded-core@lists.openembedded.org>
Subject: sstate_create_package fails since 'tar: xxxx: file changed as we read it'
Date: Thu, 8 Aug 2013 17:47:11 +0800 [thread overview]
Message-ID: <5203691F.9080306@windriver.com> (raw)
Hi All,
I met it on some packages like: util-macros-native, glib-2.0-native,
libogg ...
Build host: CentOS 5.9
Error messages:
-------------------------------
DEBUG: Preparing tree
/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/sysroot-destdir/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/sysroots/x86_64-linux
for packaging at
/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/sstate-build-populate-sysroot/x86_64-linux
NOTE: Removing hardcoded paths from sstate package: 'grep -Irl
/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/sysroots
/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/sstate-build-populate-sysroot/
| xargs grep -l -e
'/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/sysroots'
| tee /home/nxadm/nx/yow-blade4.1/builds-2013-08-0
6-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/sstate-build-populate-sysroot/fixmepath
| xargs --no-run-if-empty sed -i -e
's:/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/sysroots:FIXMESTAGINGDIR:g''
NOTE: Replacing absolute paths in fixmepath file: 'sed -i -e
's:^/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/sstate-build-populate-sysroot/::g'
/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/sstate-build-populate-sysroot/fixmepath'
DEBUG: Executing shell function sstate_create_package
tar: x86_64-linux/usr/share/aclocal/xorg-macros.m4: file changed as we
read it
WARNING:
/home/nxadm/nx/yow-blade4.1/builds-2013-08-06-030257/e500-kvm-guest_std/bitbake_build/tmp/work/x86_64-linux/util-macros-native/1_1.17-r0/temp/do_populate_sysroot/run.do_populate_sysroot.sstate_create_package.18975:122
exit 1 from
tar -czf $TFILE fixmepath x86_64-linux
DEBUG: Python function sstate_task_postfunc finished
-------------------------------
I searched and found this discussions but did not found any conclusions,
anyone know about that?
-------------------------------
JaMa anyone seeing: 11:40
JaMa | DEBUG: Executing shell function sstate_create_package 11:40
JaMa | tar: x86_64-linux/usr/share/aclocal/lib-prefix.m4: file changed
as we read it 11:40
JaMa ? I've found
http://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg36323.html
but without solution 11:40
JaMa it happens in different recipes, so far all were -native
RP JaMa: relatively old OS? 21:26
JaMa RP: no Ubuntu 12.04 22:15
JaMa and it started suddenly few days ago even on different machines
-------------------------------
Thanks
Wenzong
reply other threads:[~2013-08-08 9:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5203691F.9080306@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox