All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] gcc-cross.inc: Add depedency on BUILD_ARCH
Date: Fri, 25 Nov 2011 00:17:25 +0000	[thread overview]
Message-ID: <1322180245.10928.50.camel@ted> (raw)
In-Reply-To: <CAEsOVNe6ywzXK2b483FA-2T3A8x6-OwQXWKnsdMVWq5QTKh7sw@mail.gmail.com>

On Thu, 2011-11-24 at 23:56 +0000, McClintock Matthew-B29882 wrote:
> On Wed, Nov 23, 2011 at 3:40 AM, Matthew McClintock <msm@freescale.com> wrote:
> > +# we also add this to the PV so its clear in filenames
> > +# that this is arch specific even though it's labeled as
> > +# a target package
> > +PV .= "+${BUILD_ARCH_EXPANDED}"
> 
> Seems like based on discussion this should be the following instead:
> 
> PN .= "-{BUILD_ARCH}-${TARGET_ARCH}"

What we really want is something like this in cross.bbclass:

MULTIMACH_TARGET_SYS = "${BUILD_ARCH}${BUILD_VENDOR}-${BUILD_OS}"
PN .= "-${TRANSLATED_TARGET_ARCH}"

so that WORKDIR gets changed. I've not tested what this does to the
build though.

Also, looking at sstate.bbclass it does:

    elif bb.data.inherits_class('cross', d):
        bb.data.setVar('SSTATE_PKGARCH', bb.data.expand("${BUILD_ARCH}_${TUNE_PKGARCH}", d), d)
        bb.data.setVar('SSTATE_MANMACH', bb.data.expand("${BUILD_ARCH}_${MACHINE}", d), d)

so it should be sticking BUILD_ARCH into the sstate file name directly.
This should mean you can't use 32 bit sstate files on a 64 bit system
and vice versa already?

Cheers,

Richard





  reply	other threads:[~2011-11-25  0:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23  9:40 [RFC] gcc-cross.inc: Add depedency on BUILD_ARCH Matthew McClintock
2011-11-24  3:28 ` Khem Raj
2011-11-24  3:35   ` McClintock Matthew-B29882
2011-11-24  3:37     ` Khem Raj
2011-11-24  3:55       ` McClintock Matthew-B29882
2011-11-24  3:55         ` McClintock Matthew-B29882
2011-11-24  7:21           ` Khem Raj
2011-11-24  7:29             ` McClintock Matthew-B29882
2011-11-24 10:40               ` Richard Purdie
2011-11-24 10:54               ` Phil Blundell
2011-11-24 18:03                 ` Khem Raj
2011-11-24 18:08                   ` Phil Blundell
2011-11-24 18:29                     ` Khem Raj
2011-11-24 23:56 ` McClintock Matthew-B29882
2011-11-25  0:17   ` Richard Purdie [this message]
2011-11-25  1:52     ` McClintock Matthew-B29882
2011-11-28 22:50       ` McClintock Matthew-B29882

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=1322180245.10928.50.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B29882@freescale.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.