From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: gcc-cross-canadian-arm: found library in wrong location
Date: Thu, 07 Nov 2013 11:00:23 +0000 [thread overview]
Message-ID: <1835654.lzj3BL3FA0@helios> (raw)
In-Reply-To: <CAFyqS9rjGZ82fxov1BFux6zUv4Z+Ub+Bahinqdew9ZxTTsMV-w@mail.gmail.com>
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@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.
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.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-11-07 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 11:32 gcc-cross-canadian-arm: found library in wrong location Hans Beckérus
2013-11-07 9:56 ` Hans Beckérus
2013-11-07 11:00 ` Paul Eggleton [this message]
2013-11-07 11:15 ` Hans Beckérus
2013-11-07 14:01 ` Richard Purdie
2013-11-07 14:11 ` Hans Beckérus
2013-11-08 8:23 ` Hans Beckérus
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=1835654.lzj3BL3FA0@helios \
--to=paul.eggleton@linux.intel.com \
--cc=hans.beckerus@gmail.com \
--cc=yocto@yoctoproject.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.