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

[Hans Beckérus]

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-gnueabi/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-gnueabi/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-gnueabi/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?

We do not tell our bitbake to search in meta-opemembedded/toolchain-layer?
This is our current setting of BBLAYERS in bblayers.conf:

BBLAYERS ?= " \
  /home/user/poky/meta \
  /home/user/poky/meta-yocto \
  /home/user/poky/meta-yocto-bsp \
  /home/user/poky/meta-openembedded/meta-oe \
  "

Even if we can get some understanding of why the wrong gcc is picked
up, the QA issue might still be there of course.
But the selection of gcc version from meta-openembedded currently
seems even more strange at the moment.


> Thanks.
> Hans
>
> ---
>
> Build Configuration:
> BB_VERSION        = "1.20.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "SUSE-LINUX-11"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "zynq-zc706"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.5"
> TUNE_FEATURES     = "armv7a vfp cortexa9"
> TARGET_FPU        = "vfp"
> meta
> meta-yocto
> meta-yocto-bsp    = "dora:75bed4086eb83f1d24c31392f3dd54aa5c3679b1"
> meta-oe           = "dora:513e7ca20ddd0a5c3b649bf292a67c3e0473d3a8"