On Fri, Aug 17, 2012 at 12:12 AM, Khem Raj <raj.k...@gmail.com> wrote:
> On Thu, Aug 16, 2012 at 12:37 PM, McClintock Matthew-B29882
> <b29...@freescale.com> wrote:
>> On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj <raj.k...@gmail.com> wrote:
>>> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nyst...@enea.com> 
>>> wrote:
>>>>
>>>> Hi, it looks like this was merged to the denzil branch, and
>>>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>>>> distro.conf.
>>>> Any reason for this ?
>>>
>>> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
>>> dont expect it to have something special for SDK hosts which are
>>> usually x86 ? afterall these are for
>>> the SDK host and not for target. Moreover it means that this BSP will
>>> not play in the multi BSP environment something you never want.
>>
>> But, I think we might need them for this warning specifically:
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: multiple providers are available for lib32-linux-libc-headers
>> (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto,
>> lib32-linux-qoriq-sdk-headers)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match
>> lib32-linux-libc-headers
>> NOTE: multiple providers are available for runtime
>> lib32-linux-libc-headers-dev (lib32-linux-libc-headers,
>> lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match
>> lib32-linux-libc-headers-dev
>>
>
> This is a bug in OE-Core, it should have added appropriate defines for
> multilib case as well in
> tcmode-default.inc and default-providers.inc

And there appears to be a fix for it already:

http://patches.openembedded.org/patch/34723/

-M

>
>> ?
>>
>> -M
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to