From: Gary Thomas <gary@mlbassoc.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
Discussion of the angstrom distribution development
<angstrom-distro-devel@linuxtogo.org>
Subject: Re: [Angstrom-devel] current build errors, OE dev branch, beagleboard-linuxtag2010-demo-image
Date: Wed, 02 Jun 2010 06:08:57 -0600 [thread overview]
Message-ID: <4C0649D9.3090908@mlbassoc.com> (raw)
In-Reply-To: <20100602065840.GI5446@jama>
On 06/02/2010 12:58 AM, Martin Jansa wrote:
> On Tue, Jun 01, 2010 at 04:24:24PM -0600, Gary Thomas wrote:
>> On 06/01/2010 04:02 PM, Martin Jansa wrote:
>>> Yes easily fixable fetch errors, those archives are download restricted
>>> and if you open those recipes you will see instruction where to download
>>> them.
>>>
>>> For cheese issue I've already replied, but without answer (about
>>> gstreamer-plugins...).
>>
>> I *did* reply; it seems to be a multi-thread build problem. When
>> I reran bitbake, it went away.
>
> Yes thanks, the point is that only important part was "Was
> gst-plugins-base built before cheese?" And Robert is still having issue
> with it.
>
> So I guess the answer would be NO and no is more likely with more
> BB_THREADS and in second run it's already built (especially if you're
> building with -k) for some other recipe, so it worked for you later.
Sorry if I wasn't clear. It did appear that cheese was being built
before the prerequisites were complete.
> I've downloaded cheese, checked configure.ac and yes it depends on
> gst-plugins-base unconditionally. I've pushed an update which adds it to
> DEPENDS (which is ensured to be built _before_ do_configure of recipe,
> RRECOMMENDS is building it too, but it can build it later then
> do_configure.
I've now tried it again, removing all the gst-* packages and verified
that they are complete before cheese is built.
>
> BTW: cheese_2.30.0.bb also depends on whatever -native recipe provides
> xml2po and cheese_2.30.1.bb depends on scrollkeeper-config to build it's
> help. But probably is using happily scrollkeeper from host (as there is
> no recipe) - and I don't have scrollkeeper in my OE chroot..
> http://tinderbox.openembedded.net/packages/cheese/
>
> Robert: If I remember right, you were asked few times to use tinderbox
> instead sending many e-mails with pastebins, why didn't you follow this
> advise yet?
>
> Regards.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2010-06-02 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1006011641480.17094@lynx>
[not found] ` <4C057DFC.6010409@mlbassoc.com>
[not found] ` <alpine.DEB.2.00.1006011753350.30834@lynx>
[not found] ` <20100601220233.GG5446@jama>
[not found] ` <4C058898.60202@mlbassoc.com>
2010-06-02 6:58 ` [Angstrom-devel] current build errors, OE dev branch, beagleboard-linuxtag2010-demo-image Martin Jansa
2010-06-02 7:54 ` Robert P. J. Day
2010-06-02 12:08 ` Gary Thomas [this message]
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=4C0649D9.3090908@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.