All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@pokylinux.org>
Subject: Re: A question about overrides
Date: Wed, 10 Nov 2010 21:42:01 +0800	[thread overview]
Message-ID: <1289396521.1272.294.camel@rex> (raw)
In-Reply-To: <4CD3EF04.8030208@mlbassoc.com>

On Fri, 2010-11-05 at 05:48 -0600, Gary Thomas wrote:
> I have my own distribution layer, built on the poky distribution.
> In other words, my layer defines a few basic setups, then inherits
> poky to do the rest.
> 
> For the most part, I've been successful with this.  The problem at
> hand is that for my distribution, I need to support a couple of
> different architectures and at the moment, one of them needs to
> stay in the stone age tools-wise.  In my distro.conf, I have
> lines like these to select those tools for just that architecture:
>    GCCVERSION_armv7a ?= "4.3.3"
> This works for everything (I've tried), except this:
>    POKYLIBC_armv7a ?= "glibc"
> 
> * Is there some magic I'm missing with regard to the 'POKYLIBC' symbol?
> * Perhaps there's some other way?
> 
> For now, I'm overriding this in local.conf, but that requires
> hand tuning that I'd like to avoid.

Can you be more specific about what your distro.conf file says? I'm
guessing you're requiring poky.conf in there? Are you setting the value
after the require and does it work if you do it beforehand?

I ask as that variable is used in a require in poky.conf, effectively
causing an immediate expansion of the variable so it needs to be set
before poky.conf, not afterwards.

Cheers,

Richard



  reply	other threads:[~2010-11-10 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 11:48 A question about overrides Gary Thomas
2010-11-10 13:42 ` Richard Purdie [this message]
2010-11-10 14:03   ` Gary Thomas

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=1289396521.1272.294.camel@rex \
    --to=rpurdie@linux.intel.com \
    --cc=gary@mlbassoc.com \
    --cc=poky@pokylinux.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.