From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] icecc improvements
Date: Sat, 18 Jan 2014 15:01:50 +0100 [thread overview]
Message-ID: <cover.1390052402.git.Martin.Jansa@gmail.com> (raw)
Fix for icecc inherit causing allarch and native recipes to have different
signatures for different MACHINES.
Make blacklist more strict and start with empty one - old entries seem all
to be resolved already.
The following changes since commit 8163854adf87ac42a8f08ee25685d0ce1efb4724:
oe-selftest: separated the SStateBase and SStateTests in different modules (2014-01-16 12:18:44 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib jansa/icecc
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/icecc
Martin Jansa (4):
icecc: Don't replace non-empty PARALLEL_MAKE with empty
ICECC_PARALLEL_MAKE
icecc: use bb.utils.which also for 'as'
icecc: Fix allarch and native recipes having different signatures
icecc: use exact match in blacklists, re-start with empty
system_package_blacklist
meta/classes/icecc.bbclass | 46 +++++++++++++++++++++++++++++-----------------
1 file changed, 29 insertions(+), 17 deletions(-)
--
1.8.5.2
next reply other threads:[~2014-01-18 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 14:01 Martin Jansa [this message]
2014-01-18 14:01 ` [PATCH 1/4] icecc: Don't replace non-empty PARALLEL_MAKE with empty ICECC_PARALLEL_MAKE Martin Jansa
2014-01-18 14:01 ` [PATCH 2/4] icecc: use bb.utils.which also for 'as' Martin Jansa
2014-01-18 14:01 ` [PATCH 3/4] icecc: Fix allarch and native recipes having different signatures Martin Jansa
2014-01-18 14:01 ` [PATCH 4/4] icecc: use exact match in blacklists, re-start with empty system_package_blacklist 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=cover.1390052402.git.Martin.Jansa@gmail.com \
--to=martin.jansa@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 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.