[yocto] gcc-cross-canadian-arm: found library in wrong location

[Hans Beckérus]

On Thu, Nov 7, 2013 at 3:11 PM, Hans Beckérus <hans.beckerus at gmail.com> wrote:
> On Thu, Nov 7, 2013 at 3:01 PM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
>> On Thu, 2013-11-07 at 12:15 +0100, Hans Beckérus wrote:
>>> On Thu, Nov 7, 2013 at 12:00 PM, Paul Eggleton
>>> <paul.eggleton at linux.intel.com> wrote:
>>> > Hi Hans,
>>> >
>>> > On Thursday 07 November 2013 10:56:17 Hans Beckérus wrote:
>>> >> On Wed, Nov 6, 2013 at 12:32 PM, Hans Beckérus <hans.beckerus at gmail.com>
>>> >> wrote:
>>> >> > Hi, I am getting the below error when populating the sdk for our Yocto
>>> >> > 1.5 based image.
>>> >> >
>>> >> > WARNING: QA Issue: gcc-cross-canadian-arm: found library in wrong
>>> >> > location:
>>> >> > /opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gn
>>> >> > ueabi/gcc/arm-poky-linux-gnueabi/4.8.1/liblto_plugin.so.0.0.0
>>> >> > gcc-cross-canadian-arm: found library in wrong location:
>>> >> > /opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnu
>>> >> > eabi/gcc/arm-poky-linux-gnueabi/4.8.1/liblto_plugin.so.0
>>> >> > gcc-cross-canadian-arm: found library in wrong location:
>>> >> > /opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnu
>>> >> > eabi/gcc/arm-poky-linux-gnueabi/4.8.1/liblto_plugin.so
>>> >> >
>>> >> > Never got this on Yocto 1.4. I am not even planning of installing
>>> >> > anything in /opt so this really came out of nowhere. There is nothing
>>> >> > installed in /opt at the moment.
>>> >> > Did it actually expect to find something in /opt? And in that case,
>>> >> > how can it? It can not know where the toolchain will be installed!?
>>> >> > Somebody that can shed some light on this one? Can we safely ignore it?
>>> >>
>>> >> Ok, I started to look some more into this but unfortunately my
>>> >> knowledge about how bitbake is picking up recipes etc. is way too
>>> >> limited to explain why this is happening. I searched for
>>> >> gcc-cross-canadian in our layers and it can be found here:
>>> >>
>>> >> meta/recipes-devtools/gcc/gcc-cross-canadian.inc
>>> >> meta/recipes-devtools/gcc/gcc-cross-canadian_4.7.bb
>>> >> meta/recipes-devtools/gcc/gcc-cross-canadian_4.8.bb
>>> >> meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-cross-canadian_4.
>>> >> 6.bb
>>> >>
>>> >> So, my question now is: why does it pickup gcc 4.6 from
>>> >> meta-openembedded when there are better alternatives in oe-core?
>>> >
>>> > What makes you think it is picking up the one in toolchain-layer? I don't see
>>> > references to 4.6 in the QA error. If you haven't added meta-
>>> > openembedded/toolchain-layer to your bblayers.conf specifically it won't be
>>> > being seen by bitbake at all.
>>> >
>>>
>>> Hi Paul.
>>>
>>> True. It was a false statement. The reason behind why I thought it
>>> picked up the wrong recipe was due to other reasons.
>>> I now see that it seems to pick up the 4.8 version in oe-core.
>>>
>>> > It's more than likely that this QA error is bogus. The "found library in wrong
>>> > location" QA check was broken originally; I "fixed" it but I think it has
>>> > always been a little over-zealous since then.
>>> >
>>> I see. Funny though that this was not seen on Yocto 1.4? But it
>>> probably has a good explanation too.
>>> The most important thing is that we can now conclude that it is safe
>>> to ignore it. I guess it might have something to do with providing
>>> references to ${SDKPATH} in EXTRA_OECONF_PATHS. But it is most likely
>>> not worth the effort trying to fix it.
>>>
>>
>> There were some changes in the cross-canadian recipes in 1.5 which
>> triggered this warning. We do need to figure out why its happening and
>> fix it. It does seem to be intermittent though and when I have time to
>> debug it, I can't see to reproduce it :/
>>
> Hi Richard.
> If you wish, I can get try to reproduce it again. Only seen it once,
> but also only tried it once.
> So currently in our setup it is 100% reproducible ;)
>

It seems we get it every time in our setup.
All that is needed is:
# bitbake -c cleanall gcc-cross-canadian-arm
# bitbake gcc-cross-canadian-arm

Thanks.
Hans

>> It is relatively harmless but would be good to resolve it.
>>
>> Cheers,
>>
>> Richard
>>