From: Alex Franco <alejandro.franco@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: joshua.g.lock@intel.com, benjamin.esquivel@intel.com, aschultz@tpip.net
Subject: Re: [PATCH] nativesdk-buildtools-perl-dummy.bb: disable ICECC
Date: Tue, 22 Mar 2016 10:40:33 -0600 [thread overview]
Message-ID: <56F17581.70809@linux.intel.com> (raw)
In-Reply-To: <1458664665-20517-1-git-send-email-alejandro.franco@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1253 bytes --]
Fix originally submitted on bugzilla [1] by Andreas Schultz, I get good
results with it and I do think that ICECC should be disabled for this
recipe...
Alex Franco
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8934
On 03/22/2016 10:37 AM, Alex Franco wrote:
> Disable ICECC, as this recipe was added for compatibility with
> the extensible SDK (eSDK), and therefore does not need to be
> able to be built with the distributed icecream compiler.
>
> [YOCTO #8934]
>
> Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com>
> ---
> meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb b/meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb
> index 90784a9..b488b03 100644
> --- a/meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb
> +++ b/meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb
> @@ -18,6 +18,7 @@ PERLPACKAGES = "nativesdk-perl \
> nativesdk-perl-module-file-path"
>
> ALLOW_EMPTY_${PN} = "1"
> +ICECC_DISABLED = "1"
>
> python populate_packages_prepend() {
> d.appendVar(d.expand('RPROVIDES_${PN}'), '${PERLPACKAGES}')
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2016-03-22 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 16:37 [PATCH] nativesdk-buildtools-perl-dummy.bb: disable ICECC Alex Franco
2016-03-22 16:40 ` Alex Franco [this message]
2016-03-22 16:41 ` Burton, Ross
2016-03-22 16:45 ` Burton, Ross
2016-03-22 18:21 ` Alex Franco
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=56F17581.70809@linux.intel.com \
--to=alejandro.franco@linux.intel.com \
--cc=aschultz@tpip.net \
--cc=benjamin.esquivel@intel.com \
--cc=joshua.g.lock@intel.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