From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Last update breaks build
Date: Fri, 31 Aug 2012 17:38:42 +0100 [thread overview]
Message-ID: <1409702.3ge2L51VIb@helios> (raw)
In-Reply-To: <CALbNGRT51iB+D_7ShwYYx=KzDL=uafR_WTyYwQyjU+OSyFzknA@mail.gmail.com>
On Friday 31 August 2012 18:30:55 Andreas Müller wrote:
> Hi,
>
> since the last layer updates I am not able to build. First I got
>
> WARNING: Consider updating kde-artwork-active recipe to use "protocol"
> not "proto" in SRC_URI.
>
> | ETA: 00:01:13
>
> WARNING: OPIE_VERSION has not been set; if you are going to build
> Opie, you need to 'require' an appropriate .inc file from
> meta-opie/conf/distro/include |
> ETA: 00:01:47
> ERROR: Error executing a python function in <code>:
> ExpansionError: Failure expanding variable FILESPATH, expression was
> ${@base_set_filespath([
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-reloa
> d/opie-icon-reload-0-${OPIE_SRCREV}-r0",
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-relo
> ad/opie-icon-reload-0-${OPIE_SRCREV}",
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-relo
> ad/opie-icon-reload",
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-relo
> ad/opie-icon-reload-0-${OPIE_SRCREV}",
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-relo
> ad/opie-icon-reload",
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-relo
> ad/files",
> "/home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-relo
> ad" ], d)} which triggered exception SyntaxError: EOL while scanning
> string literal (FILESPATH, line 1)
>
> ERROR: The stack trace of python calls that resulted in this
> exception/failure was:
> ERROR: File "<code>", line 2, in <module>
> ERROR:
> ERROR: File
> "__anon_564__home_Superandy_data_oe_core_sources_openembedded_core_meta_cla
> sses_base_bbclass", line 200, in
> __anon_564__home_Superandy_data_oe_core_sources_openembedded_core_meta_clas
> ses_base_bbclass ERROR:
> ERROR: File
> "/home/Superandy/oe-core/sources/bitbake/lib/bb/data_smart.py", line 290,
> in getVar
> ERROR: return self.expand(value, var)
> ERROR:
> ERROR: File
> "/home/Superandy/oe-core/sources/bitbake/lib/bb/data_smart.py", line 154,
> in expand
> ERROR: return self.expandWithRefs(s, varname).value
> ERROR:
> ERROR: File
> "/home/Superandy/oe-core/sources/bitbake/lib/bb/data_smart.py", line 144,
> in expandWithRefs
> ERROR: raise ExpansionError(varname, s, exc)
> ERROR:
> ERROR: The code that was being executed was:
> ERROR:
> 0001:__anon_125__home_Superandy_data_oe_core_sources_openembedded_core_meta
> _classes_staging_bbclass(d) ERROR: ***
> 0002:__anon_564__home_Superandy_data_oe_core_sources_openembedded_core_meta
> _classes_base_bbclass(d) ERROR:
> 0003:__anon_218__home_Superandy_data_oe_core_sources_openembedded_core_meta
> _classes_package_bbclass(d) ERROR:
> 0004:__anon_452__home_Superandy_data_oe_core_sources_openembedded_core_meta
> _classes_package_ipk_bbclass(d) ERROR:
> 0005:__anon_756__home_Superandy_data_oe_core_sources_openembedded_core_meta
> _classes_insane_bbclass(d) ERROR:
> 0006:__anon_20__home_Superandy_data_oe_core_sources_openembedded_core_meta_
> classes_debian_bbclass(d) ERROR: [From file: '<code>', lineno: 2, function:
> <module>]
> ERROR: 0196: #
> ERROR: 0197: override = d.getVar('SRC_URI_OVERRIDES_PACKAGE_ARCH',
> True) ERROR: 0198: if override != '0':
> ERROR: 0199: paths = []
> ERROR: *** 0200: fpaths = (d.getVar('FILESPATH', True) or
> '').split(':') ERROR: 0201: machine = d.getVar('MACHINE', True)
> ERROR: 0202: for p in fpaths:
> ERROR: 0203: if os.path.basename(p) == machine and
> os.path.isdir(p):
> ERROR: 0204: paths.append(p)
> ERROR: [From file:
> '__anon_564__home_Superandy_data_oe_core_sources_openembedded_core_meta_clas
> ses_base_bbclass', lineno: 200, function:
> __anon_564__home_Superandy_data_oe_core_sources_openembedded_core_meta_class
> es_base_bbclass] ERROR: Failed to parse recipe:
> /home/Superandy/data/oe-core/sources/meta-opie/recipes-opie/opie-icon-reload
> /opie-icon-reload_git.bb WARNING: OPIE_VERSION has not been set; if you are
> going to build
> Opie, you need to 'require' an appropriate .inc file from
> meta-opie/conf/distro/include
> ERROR: Command execution failed: Exited with 1
>
>
> After removing meta-opie I now get
>
> ERROR: OE-core's config sanity checker detected a potential
> misconfiguration. Either fix the cause of this error or at your own risk
> disable the checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> DISTRO 'angstrom-v2012.x' not found. Please set a valid DISTRO in
> your local.conf
>
> ERROR: Execution of event handler 'check_sanity_eventhandler' failed
> ERROR: Command execution failed: Exited with 1
>
> Do we have now poky world domination?
Er, don't blame poky for the rename of angstrom-2012.x to angstrom-next in
meta-angstrom master...
(Although granted, this error spew is rather nasty and hides the actual
problem.)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-08-31 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 16:30 Last update breaks build Andreas Müller
2012-08-31 16:38 ` Paul Eggleton [this message]
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=1409702.3ge2L51VIb@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox