Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alex Franco <alejandro.franco@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Joshua G Lock <joshua.g.lock@intel.com>,
	Benjamin Esquivel <benjamin.esquivel@intel.com>,
	Andreas Schultz <aschultz@tpip.net>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nativesdk-buildtools-perl-dummy.bb: disable ICECC
Date: Tue, 22 Mar 2016 12:21:37 -0600	[thread overview]
Message-ID: <56F18D31.8020402@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaLRwcuY=-BJcRDUm9Y5Y_umixeq=Zm3NUL+2XTbBTxaw@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1619 bytes --]

Ross, I suppose you mean " icc_is_allarch()" ?

Ok , so this recipe does inherit allarch but it is sort of nativesdk,
and when the test icc_is_allarch() checks for the value of
'PACKAGE_ARCH', it gets "buildtools-dummy-${SDKPKGSUFFIX}" (which should
expand to 'buildtools-dummy-nativesdk', but doesn't) instead of the
expected "all".

I am now modifying this test to check for an inherit of allarch, and
playing a bit with this. I'll keep you posted.

Other stuff to consider:

- Expand the value of PACKAGE_ARCH if necessary? I am doing it now as
part of my tests but not sure I will be committing this:

     package_arch = d.getVar("PACKAGE_ARCH", False)
     if '${' in package_arch:
         package_arch = d.expand(package_arch)
    ...

- All of these functions in the icecc.bbclass that incude "icc" in their
names, should probably be modified to say "icecc" instead. As it stands
now, it can cause confusion as some people might think we're talking
about the intel c compiler rather than the icecream compiler - I wonder
if there's a bug for this already

Alex Franco

On 03/22/2016 10:45 AM, Burton, Ross wrote:
>
> On 22 March 2016 at 16:41, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
>     Do we understand why this recipe breaks the icecc class?
>
>
> So I'm guessing it's because the architecture of the recipe is
> "special" - it's sort-of allarch and sort of nativesdk.
>
> I wonder if changing the icecc_is_allarch() test to check for inherit
> of allarch would fix this without working around the problem.
>
> Ross 
>


[-- Attachment #1.1.2: Type: text/html, Size: 2995 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

      reply	other threads:[~2016-03-22 18:20 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
2016-03-22 16:41   ` Burton, Ross
2016-03-22 16:45     ` Burton, Ross
2016-03-22 18:21       ` Alex Franco [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=56F18D31.8020402@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 \
    --cc=ross.burton@intel.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