gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Jacob Kroon]

[-- 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 --]

Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Otavio Salvador]

Hello Jacob,

On Sun, Jun 29, 2014 at 10:08 AM, Jacob Kroon <jacob.kroon@gmail.com> wrote:
> 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.

In fact I think it needs a 'depends' so it can resolve the runtime
dependency at this time.

Prabhu, can you confirm gpu-viv-bin-mx6q uses libffi?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Prabhu.Sundararaj]

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.

Best Regards,
Prabhu

-----Original Message-----
From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On Behalf Of Otavio Salvador
Sent: Monday, June 30, 2014 7:13 AM
To: Jacob Kroon; Sundararaj Prabhu-B36876
Cc: meta-freescale
Subject: Re: [meta-freescale] gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

Hello Jacob,

On Sun, Jun 29, 2014 at 10:08 AM, Jacob Kroon <jacob.kroon@gmail.com> wrote:
> 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.

In fact I think it needs a 'depends' so it can resolve the runtime dependency at this time.

Prabhu, can you confirm gpu-viv-bin-mx6q uses libffi?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Otavio Salvador]

On Mon, Jun 30, 2014 at 9:29 AM, Prabhu.Sundararaj@freescale.com
<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?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Jacob Kroon]

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

On Mon, Jun 30, 2014 at 2:33 PM, Otavio Salvador <otavio@ossystems.com.br>
wrote:

> On Mon, Jun 30, 2014 at 9:29 AM, Prabhu.Sundararaj@freescale.com
> <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

[-- Attachment #2: Type: text/html, Size: 1913 bytes --]

Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Otavio Salvador]

Hello Jacob,

On Mon, Jun 30, 2014 at 9:56 AM, Jacob Kroon <jacob.kroon@gmail.com> wrote:
> On Mon, Jun 30, 2014 at 2:33 PM, Otavio Salvador <otavio@ossystems.com.br>
> wrote:
>>
>> On Mon, Jun 30, 2014 at 9:29 AM, Prabhu.Sundararaj@freescale.com
>> <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 ?

Yes.

> I think this is what OE's automatic dependency-scanner is picking up, and
> why there is this churn in the buildhistory logs.

You're right.

I think that in case we're not using the Wayland backend we could drop
those files I think.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?

[Jacob Kroon]

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

Hi Otavio,

On Mon, Jun 30, 2014 at 3:46 PM, Otavio Salvador <otavio@ossystems.com.br>
wrote:

> Hello Jacob,
>
> On Mon, Jun 30, 2014 at 9:56 AM, Jacob Kroon <jacob.kroon@gmail.com>
> wrote:
> > On Mon, Jun 30, 2014 at 2:33 PM, Otavio Salvador <
> otavio@ossystems.com.br>
> > wrote:
> >>
> >> On Mon, Jun 30, 2014 at 9:29 AM, Prabhu.Sundararaj@freescale.com
> >> <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 ?
>
> Yes.
>
> > I think this is what OE's automatic dependency-scanner is picking up, and
> > why there is this churn in the buildhistory logs.
>
> You're right.
>
> I think that in case we're not using the Wayland backend we could drop
> those files I think.
>
>
I just sent a patch to ml, adding libffi as a DEPENDS. But maybe I was
acting hastily here. Are you
suggesting that we should only generate those packages that correspond to
actually enabled distro features ?
If it is possible, I could try and do it like that, since that would also
get rid of the buildhistory churn I'm getting.
(Since I'm not using Wayland)

/Jacob

[-- Attachment #2: Type: text/html, Size: 3042 bytes --]