From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] meta/icecc.bbclass: Update system blacklists
Date: Tue, 20 Nov 2018 14:04:16 -0600 [thread overview]
Message-ID: <20181120200416.15895-3-JPEWhacker@gmail.com> (raw)
In-Reply-To: <20181120200416.15895-1-JPEWhacker@gmail.com>
Updates the system blacklists to include packages that are known to have
problems compiling under icecream
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
meta/classes/icecc.bbclass | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index 037cce1e964..2b189232cb7 100644
--- a/meta/classes/icecc.bbclass
+++ b/meta/classes/icecc.bbclass
@@ -68,14 +68,22 @@ ICECC_ENV_DEBUG ??= ""
#
# libgcc-initial - fails with CPP sanity check error if host sysroot contains
# cross gcc built for another target tune/variant
+# target-sdk-provides-dummy - ${HOST_PREFIX} is empty which triggers the "NULL
+# prefix" error.
ICECC_SYSTEM_PACKAGE_BL += "\
libgcc-initial \
+ target-sdk-provides-dummy \
"
# "system" classes that should be blacklisted. When adding new entry, please
# document why (how it failed) so that we can re-evaluate it later
#
+# image - Image aren't compiling, but the testing framework for images captures
+# PARALLEL_MAKE as part of the test environment. Many tests won't use
+# icecream, but leaving the high level of parallelism can cause them to
+# consume an unnecessary amount of resources.
ICECC_SYSTEM_CLASS_BL += "\
+ image \
"
def icecc_dep_prepend(d):
--
2.19.1
prev parent reply other threads:[~2018-11-20 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:04 [PATCH 0/2] Update icecream blacklists Joshua Watt
2018-11-20 20:04 ` [PATCH 1/2] meta/icecc.bbclass: Move system blacklist to variables Joshua Watt
2018-11-20 20:04 ` Joshua Watt [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=20181120200416.15895-3-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.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