On 11/10/2010 06:42 AM, Richard Purdie wrote:
> 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.

Yes, I do have a require poky.conf and I'm setting these variables
before that statement.

I've attached the files I use (slightly sanitized).  Note that the only
way I could work this out was to define POKYLIBC in local.conf

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------