From: Jean-Charles <jicheu@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: dleyna not building
Date: Wed, 09 Oct 2013 17:07:35 +0200 [thread overview]
Message-ID: <52557137.3080405@gmail.com> (raw)
In-Reply-To: <CAJTo0LbOfVAuzo_XBikdnssxe52OQ-KNbiqq5u1JkBnSJBFZ_Q@mail.gmail.com>
On 09/10/2013 16:59, Burton, Ross wrote:
> On 9 October 2013 12:48, Jean-Charles <jicheu@gmail.com> wrote:
>> Anyone tried to build dleyna recently ? The do_configure invariably fails on
>> dylan (with a very long configure log but nothing obvious.. however a simple
>> "bitbake media-service-upnp" will lead to the same error.
>>
>> I suspect the package is somewhat outdate as I had to change the MD5 to be
>> able to build it:
>>
>> -SRC_URI[md5sum] = "9fc4db84b3459bc77232b24bde48b000"
>> -SRC_URI[sha256sum] =
>> "9cdee47bbbfa3de5aaa5cf3fc9e208ccd97e5079f6d8fa84a6d1f24a1b760237"
>> +SRC_URI[md5sum] = "eb7d58a429184180fdc48330bba9bb45"
>> +SRC_URI[sha256sum] =
>> "979661e4828a23292f05e9b82707d291fe2a63eeddcde0150a2f09c5c060847f"
> That's github re-generating tarballs underneath us - this was fixed in
> meta-oe master by changing it to do a git clone. If you're using the
> dylan stable branch you can cherry-pick that commit from master.
>
> Then if you still get problems please paste the full logs, as I built
> it all recently when changing the SRC_URI.
>
> Ross
the issue is with gssdp :
>> configure: error: Package requirements (gssdp-1.0 >= 0.13.2) were
not met:
>> Requested 'gssdp-1.0 >= 0.13.2' but version of gssdp-1.0 is 0.12.2.1
There are both recipes on meta-multimedia, why would it take the older
one :( ?
next prev parent reply other threads:[~2013-10-09 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 11:48 dleyna not building Jean-Charles
2013-10-09 14:59 ` Burton, Ross
2013-10-09 15:03 ` Jean-Charles
2013-10-09 15:07 ` Jean-Charles [this message]
2013-10-09 15:11 ` Burton, Ross
2013-10-09 15:15 ` Jean-Charles
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=52557137.3080405@gmail.com \
--to=jicheu@gmail.com \
--cc=ross.burton@intel.com \
--cc=yocto@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.