From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] gstreamer1.0-plugins-imx: Update to version 0.12.0
Date: Thu, 14 Jan 2016 09:51:41 +0100 [thread overview]
Message-ID: <5697619D.1030000@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKq_D6cH4dWhg+oQzP_aZjZzhjEzf01XLiccb+P=3-pu1Q@mail.gmail.com>
Nothing anywhere in gstreamer-imx contains anything about libfslvpuwrap.
This is really puzzling. I also checked the SRCREV in the revision
number, and it is correct.
Can you send me a tarball with the contents of
tmp/work/...-linux-gnueabi/gstreamer1.0-plugins-imx/0.12.0+AUTOINC+d7c1e7f041-r0/
? In other words, the entire work folder of that build.
On 2016-01-13 22:09, Otavio Salvador wrote:
> On Wed, Jan 13, 2016 at 5:42 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> This makes no sense. The new version does _not_ look for libfslvpuwrap.
>> Checking the log.do_configure output of my local build confirms this.
>> Perhaps for some reason the older 0.11.1 version is being used?
> I checked the source code and it does not seem to look at it indeed.
> However it failed on this recipe.
>
> Would be possible the code is auto-detecting its availability and
> enabling something?
>
next prev parent reply other threads:[~2016-01-14 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 8:43 [meta-fsl-arm][PATCH] gstreamer1.0-plugins-imx: Update to version 0.12.0 Carlos Rafael Giani
2016-01-08 8:44 ` Carlos Rafael Giani
2016-01-13 19:38 ` Otavio Salvador
2016-01-13 19:42 ` Carlos Rafael Giani
2016-01-13 21:09 ` Otavio Salvador
2016-01-14 8:51 ` Carlos Rafael Giani [this message]
2016-01-14 21:26 ` Otavio Salvador
2016-01-21 19:34 ` Otavio Salvador
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=5697619D.1030000@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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.