From: Jacob Kroon <jacob.kroon@gmail.com>
To: meta-freescale <meta-freescale@yoctoproject.org>
Subject: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?
Date: Sun, 29 Jun 2014 15:08:12 +0200 [thread overview]
Message-ID: <CAPbeDCkHWOOBeTNFVak8TDfmj2FJOH+xgjzQ66WbVDrFHs3Z5A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Hello,
I'm seeing some unexplained changes in the buildhistory when I do
incremental builds of the SD-images. The wayland packages from
gpu-viv-bin-mx6q recipe seem to have an unspecified dependency on libffi:
PKG = libwayland-viv0
RPROVIDES =
-RDEPENDS = eglibc (>= 2.19)
+RDEPENDS = eglibc (>= 2.19) libffi (>= 3.0.13)
Several of the dev/debug-packages also have this change:
libegl-dbg
libgc-wayland-protocol-dbg
libgc-wayland-protocol-dev
libgc-wayland-protocol0
libgl-dbg
libglesv2-dbg
libwayland-viv-dbg
libwayland-viv-dev
libwayland-viv0
Looking into log.do_package I see:
log.do_package:DEBUG: libwayland-viv-mx6: Dependency libffi.so.6 requires
package libffi
log.do_package:DEBUG: libgc-wayland-protocol-mx6: Dependency libffi.so.6
requires package libffi
In what I think is one of the older log-files I see this:
NOTE: Couldn't find shared library provider for libffi.so.6, used by
files: [...]
So it seems to me that some of the sub-packages needs a RDEPEND on libffi.
/Jacob
[-- Attachment #2: Type: text/html, Size: 1252 bytes --]
next reply other threads:[~2014-06-29 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 13:08 Jacob Kroon [this message]
2014-06-30 12:13 ` gpu-viv-bin-mx6q: missing RDEPENDS on libffi ? Otavio Salvador
2014-06-30 12:29 ` Prabhu.Sundararaj
2014-06-30 12:33 ` Otavio Salvador
2014-06-30 12:56 ` Jacob Kroon
2014-06-30 13:46 ` Otavio Salvador
2014-07-16 23:49 ` Jacob Kroon
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=CAPbeDCkHWOOBeTNFVak8TDfmj2FJOH+xgjzQ66WbVDrFHs3Z5A@mail.gmail.com \
--to=jacob.kroon@gmail.com \
--cc=meta-freescale@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.