From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-devel@lists.openembedded.org>
Subject: meta-openembedded "toolchain-layer" is broken
Date: Wed, 7 Oct 2015 09:30:02 +0200 [thread overview]
Message-ID: <5614C9FA.20703@topic.nl> (raw)
If you happen to have "toolchain-layer" in your bblayer list, it will trigger
this:
ERROR: ExpansionError during parsing
.../meta-oe/toolchain-layer/recipes-devtools/gcc/gcc-crosssdk_4.6.bb: Failure
expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which
triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid
SCM was found in SRC_URI
I just happened to notice. Maybe it's time to take gcc 4.6 to the glue factory?
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next reply other threads:[~2015-10-07 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 7:30 Mike Looijmans [this message]
2015-10-08 1:33 ` meta-openembedded "toolchain-layer" is broken Khem Raj
2015-10-08 5:39 ` [meta-oe][toolchain-layer][PATCH] Remove toolchain-layer Mike Looijmans
2015-10-09 7:12 ` Khem Raj
2015-10-09 9:06 ` Philip Balister
2015-10-09 9:11 ` Martin Jansa
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=5614C9FA.20703@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-devel@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