Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] native.bbclass: Ensure native recipes have a deterministic baselib value
Date: Thu, 06 Oct 2011 22:47:49 +0100	[thread overview]
Message-ID: <1317937677.6398.130.camel@ted> (raw)
In-Reply-To: <4E8DBF9E.70600@windriver.com>

On Thu, 2011-10-06 at 09:47 -0500, Mark Hatle wrote:
> On 10/6/11 9:20 AM, Richard Purdie wrote:
> > Changes to baselib by specific machine configuration were resulting
> > in sstate cache invalidation, particularly in multilib configurations.
> > 
> > This patch ensures this doesn't happen and native sstate cache files
> > are reusable.
> 
> Likely throwing in a can of worms here, but for our existing (non-OE based)
> work, we generally change the baselib to "lib64" on 64-bit machines.  Without
> patching native.bbclass, is it possible to do that?

Yes, you could set this based on the build system architecture no
problem at all.

The reason for this change is to have a single value for native packages
which doesn't change based on MACHINE. That doesn't stop you changing it
based on something specific the native binaries themselves.

The native sysroots are different depending on the build system
architecture anyway so this actually might be a non-issue for you
anyway.

Cheers,

Richard




  reply	other threads:[~2011-10-06 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 14:20 [PATCH] native.bbclass: Ensure native recipes have a deterministic baselib value Richard Purdie
2011-10-06 14:47 ` Mark Hatle
2011-10-06 21:47   ` Richard Purdie [this message]
2011-10-06 21:01 ` 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=1317937677.6398.130.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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