All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Jacob Kroon <jacob.kroon@gmail.com>
Cc: meta-freescale <meta-freescale@yoctoproject.org>,
	"Prabhu.Sundararaj@freescale.com"
	<Prabhu.Sundararaj@freescale.com>
Subject: Re: gpu-viv-bin-mx6q: missing RDEPENDS on libffi ?
Date: Mon, 30 Jun 2014 10:46:31 -0300	[thread overview]
Message-ID: <CAP9ODKo13LdNU-swx0AnGWPfYaiGnUHyHdVgB65sCuwk4a21HQ@mail.gmail.com> (raw)
In-Reply-To: <CAPbeDCk0UuZjVyMJdeTqurN009v_NOM6-UoDNvc-+tJ_OvjS6A@mail.gmail.com>

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


  reply	other threads:[~2014-06-30 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 13:08 gpu-viv-bin-mx6q: missing RDEPENDS on libffi ? Jacob Kroon
2014-06-30 12:13 ` 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 [this message]
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=CAP9ODKo13LdNU-swx0AnGWPfYaiGnUHyHdVgB65sCuwk4a21HQ@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=Prabhu.Sundararaj@freescale.com \
    --cc=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.