From: Phil Blundell <philb@gnu.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] eglibc: Move perl- and bash-using scripts to separate recipes
Date: Wed, 17 Oct 2012 23:56:33 +0100 [thread overview]
Message-ID: <1350514593.4470.175.camel@x121e.pbcl.net> (raw)
In-Reply-To: <507E2722.9020904@linux.intel.com>
On Tue, 2012-10-16 at 20:33 -0700, Saul Wold wrote:
> Another edge case?
> > ERROR: Function failed: do_evacuate_scripts (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-eglibc-initial-2.16-r16+svnr20393/temp/log.do_evacuate_scripts.1600 for further information)
> > ERROR: Logfile of failure stored in: /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-eglibc-initial-2.16-r16+svnr20393/temp/log.do_evacuate_scripts.1600
> > Log data follows:
> > | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i686-linux', 'common']
> > | DEBUG: Executing shell function do_evacuate_scripts
> > | cp: cannot stat `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-eglibc-initial-2.16-r16+svnr20393/image/opt/poky/1.3+snapshot/sysroots/i686-pokysdk-linux/usr/bin/mtrace': No such file or directory
> > | ERROR: Function failed: do_evacuate_scripts (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-eglibc-initial-2.16-r16+svnr20393/temp/log.do_evacuate_scripts.1600 for further information)
> > NOTE: recipe nativesdk-eglibc-initial-2.16-r16+svnr20393: task do_evacuate_scripts: Failed
> > NOTE: recipe gupnp-av-0.8.0-r2: task do_compile: Started
> > ERROR: Task 1593 (virtual:nativesdk:/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/meta/recipes-core/eglibc/eglibc-initial_2.16.bb, do_evacuate_scripts) failed with exit code '1'
>
> This was a build for the meta-toolchain-gmae, but I also saw this with
> the multilib build.
The issue with meta-toolchain-gmae is that eglibc-package.inc needs to
declare an empty do_evacuate_scripts_pn-nativesdk-eglibc-initial(), like
it does for pn-eglibc-initial. Something along the lines of:
--- a/meta/recipes-core/eglibc/eglibc-package.inc
+++ b/meta/recipes-core/eglibc/eglibc-package.inc
@@ -121,6 +121,10 @@ do_evacuate_scripts_pn-eglibc-initial () {
:
}
+do_evacuate_scripts_pn-nativesdk-eglibc-initial () {
+ :
+}
+
addtask evacuate_scripts after do_install before do_populate_sysroot do_package
PACKAGE_PREPROCESS_FUNCS += "eglibc_package_preprocess"
Do you have an easy way to reproduce the multilib failure?
p.
next prev parent reply other threads:[~2012-10-17 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 12:56 [PATCH v3] eglibc: Move perl- and bash-using scripts to separate recipes Phil Blundell
2012-10-12 17:44 ` Saul Wold
2012-10-15 9:46 ` Phil Blundell
2012-10-17 3:33 ` Saul Wold
2012-10-17 22:56 ` Phil Blundell [this message]
2012-10-18 9:59 ` Richard Purdie
2012-10-18 10:02 ` Phil Blundell
2012-10-18 22:15 ` Phil Blundell
2012-10-24 16:00 ` Saul Wold
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=1350514593.4470.175.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.