From: Denys Dmytriyenko <denys@ti.com>
To: Kovesdi Gyorgy <kgy@teledigit.eu>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: Problem compiling libgles-omap3_4.09.00.01
Date: Sat, 10 Aug 2013 13:38:20 -0400 [thread overview]
Message-ID: <20130810173820.GC27433@edge> (raw)
In-Reply-To: <1554710.Rp68v4FIpQ@kgy-pc>
On Sat, Aug 10, 2013 at 06:30:10PM +0200, Kovesdi Gyorgy wrote:
> Hi,
>
> I have no luck with libgles-omap3 too :-(
> Trying to use the recent versions of meta-ti and poky, i got the following
> error:
>
> ERROR: QA Issue: File '/usr/lib/libsrv_init.so.1.9.2188537' from libgles-omap3
> was already stripped, this will prevent future debugging!
> ....... (a lot of other similar files are mentioned here) .......
> Summary: 1 task failed:
> /home/kgy/work/Yocto/poky/meta-ti/recipes-graphics/libgles/libgles-
> omap3_4.09.00.01.bb, do_package
>
> Some time ago, this kind of QA problems was treated as warnings - as far as i
> remember. Currently i don't care about debugging, so it would also good if i
> could ignore these errors or at least switch them to warning. Is it possible?
This seems to be Poky-specific issue. Those are still warnings in
oe-core/master when built in distro-less setup, as well as in Arago distro.
You need to disable that specific QA check in your distro or local.conf to get
through. Unfortunately, most of the libraries in libgles are proprietary and
shipped in binary form that are already stripped, so this QA check will always
complain, but needs to be non fatal...
--
Denys
next prev parent reply other threads:[~2013-08-10 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 16:30 Problem compiling libgles-omap3_4.09.00.01 Kovesdi Gyorgy
2013-08-10 17:38 ` Denys Dmytriyenko [this message]
2013-08-10 17:54 ` Denys Dmytriyenko
2013-08-10 20:42 ` Kovesdi Gyorgy
2013-08-15 7:53 ` Kovesdi Gyorgy
2013-08-15 18:48 ` Denys Dmytriyenko
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=20130810173820.GC27433@edge \
--to=denys@ti.com \
--cc=kgy@teledigit.eu \
--cc=meta-ti@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.