From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4997DE006BC; Mon, 30 Jun 2014 05:56:55 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (jacob.kroon[at]gmail.com) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.217.181 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A36FAE00303 for ; Mon, 30 Jun 2014 05:56:44 -0700 (PDT) Received: by mail-lb0-f181.google.com with SMTP id p9so5735604lbv.26 for ; Mon, 30 Jun 2014 05:56:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1wNhkvhv18YewItTSNc9fNHsdx+GOW2sO3NUWt8fxM4=; b=u1JnXGA0BEFsaS1iz5Wx31k42buekUevnAEL8ZetmhBcngEW/CHu1AGmeyWE3q+78E F8brZbhS7EKOlqU8cdQg6bOy7+K0t8UdYUaLLX4dIMgggWRRb9kUePgX8FmoWzLB4MTH 6m+coRiQda4sJiOZ6vWzy0l8NosdsQEzTUeuQHhKkkOV8qtKSCMzXu9TrmofNhAgCjvK 65bOJ14+g6jmZYwpFiYzKr0tg9oxHdc2xGbeLkxYkCsEXpBS/2IEZo1jTVSCC+AOh+VM e43R7Sjc/mQXmvx6wSofzAROilRGsTA8cniFXInL/JY5xje28kZZYD6n8gSmIqMKq4gO CvPw== MIME-Version: 1.0 X-Received: by 10.112.160.197 with SMTP id xm5mr15463335lbb.24.1404133003666; Mon, 30 Jun 2014 05:56:43 -0700 (PDT) Received: by 10.112.26.211 with HTTP; Mon, 30 Jun 2014 05:56:43 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Jun 2014 14:56:43 +0200 Message-ID: From: Jacob Kroon To: Otavio Salvador Cc: meta-freescale , "Prabhu.Sundararaj@freescale.com" Subject: Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ? X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2014 12:56:55 -0000 Content-Type: multipart/alternative; boundary=001a11c25a3ce6aaeb04fd0d3062 --001a11c25a3ce6aaeb04fd0d3062 Content-Type: text/plain; charset=UTF-8 On Mon, Jun 30, 2014 at 2:33 PM, Otavio Salvador wrote: > On Mon, Jun 30, 2014 at 9:29 AM, Prabhu.Sundararaj@freescale.com > wrote: > > gpu-viv-bin-mx6q has binaries for different backends like > fbdev,X11,wayland. > > In that wayland backend binaries like libEGLso, libgc-wayland-protocol > depends on wayland and in turn wayland depends on libffi. > > > > But gpu-viv-bin-mx6q does not directly depend on libffi. > > So the DEPENDS should be added in gpu-viv-bin-mx6q when using Wayland > backend? > > Jacob, can you cook a patch for this? > > I'm not entirely satisfied with that solution I'll have to admit.. I'm not using Wayland in my builds, and I am still seeing this floating dependency in the buildhistory package data. [root@localhost lib]# arm-oe-linux-gnueabi-readelf libwayland-viv.so.0.0.0 -a|grep libffi 0x00000001 (NEEDED) Shared library: [libffi.so.6] Does this not mean that the libwayland-viv.so.0.0.0 library is in fact linked directly to libffi ? I think this is what OE's automatic dependency-scanner is picking up, and why there is this churn in the buildhistory logs. /Jacob --001a11c25a3ce6aaeb04fd0d3062 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jun 30, 2014 at 2:33 PM, Otavio Salvador <otavio@ossystems.com.= br> wrote:
On Mon, J= un 30, 2014 at 9:29 AM, = Prabhu.Sundararaj@freescale.com
<Prabhu.Sundararaj@fr= eescale.com> wrote:
> gpu-viv-bin-mx6q has binaries for different backends like fbdev,X11,wa= yland.
> In that wayland backend binaries like libEGLso, libgc-wayland-protocol= depends on wayland and in turn wayland depends on libffi.
>
> But gpu-viv-bin-mx6q does not directly depend on libffi.

So the DEPENDS should be added in gpu-viv-bin-mx6q when using Wayland= backend?

Jacob, can you cook a patch for this?


I'm = not entirely satisfied with that solution I'll have to admit.. I'm = not using Wayland in my builds, and I am still seeing
this floating depe= ndency in the buildhistory package data.

[root@localhost lib]# arm-oe-linux-gnueabi-readelf libwayland-viv= .so.0.0.0 -a|grep libffi
=C2=A00x000000= 01 (NEEDED)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Shared library: [= libffi.so.6]

Does this not mean that the libwayland-viv.so.0.0.0 library is in fact link= ed directly to libffi ?
I think this is= what OE's automatic dependency-scanner is picking up, and why there is= this churn in the buildhistory logs.

/Jacob
--001a11c25a3ce6aaeb04fd0d3062--