From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <ankur.tyagi85@gmail.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Including vendor's pre-built binary in image
Date: Wed, 8 Apr 2020 06:42:34 +0000 [thread overview]
Message-ID: <20200408064233.GE104502@korppu> (raw)
In-Reply-To: <CADySD0GO0510UjoSWx=sK9oiyCFCJanB7-C7Ph6y62BtOmfNXA@mail.gmail.com>
Hi,
On Wed, Apr 08, 2020 at 01:52:47PM +1200, Ankur Tyagi wrote:
> Hi,
>
> I am sure this is not being discussed for first time and I tried
> all suggested solution in previous emails but none worked hence I am asking
> again.
>
> Trying to include a pre-built binary from vendor in my image but getting
> following QA error:
>
> ERROR: my-recipe-1.0-r0 do_package_qa: QA Issue: /etc/vendor/tool contained
> in package my-recipe requires libstdc++.so.6(CXXABI_1.3), but no providers
> found in RDEPENDS_my-recipe ? [file-rdeps]
> ERROR: my-recipe -1.0-r0 do_package_qa: QA Issue: /etc/vendor/tool
> contained in package my-recipe requires libstdc++.so.6(GLIBCXX_3.4), but no
> providers found in RDEPENDS_my-recipe ? [file-rdeps]
> ERROR: my-recipe -1.0-r0 do_package_qa: QA run found fatal errors. Please
> consider fixing them.
> ERROR: my-recipe -1.0-r0 do_package_qa: Function failed: do_package_qa
>
> I have tried following in my-recipe_1.0.bb but error still persists
> RDEPENDS_${PN} += "libstdc++6"
This shared library comes from gcc-runtime recipe and libstdc++ binary package
(before name manglings). buildhistory helps with cases like this.
I would write recipes for all binaries and make sure all QA checks are passing
with them. Best way is to get vendors to compile with your SDK.
Cheers,
-Mikko
>
> How can I fix this?
>
> thanks
> Ankur
>
next prev parent reply other threads:[~2020-04-08 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 1:52 Including vendor's pre-built binary in image Ankur Tyagi
2020-04-08 6:42 ` Mikko Rapeli [this message]
2020-04-08 10:38 ` [OE-core] " Ankur Tyagi
2020-04-08 7:12 ` Denys Dmytriyenko
2020-04-08 10:40 ` Ankur Tyagi
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=20200408064233.GE104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=ankur.tyagi85@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox