From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE weekly changelog 2009-07-13 to 2009-07-20 - Bluetooth still not working
Date: Wed, 22 Jul 2009 11:42:43 +0200 [thread overview]
Message-ID: <4A66DF13.2030907@atmel.com> (raw)
In-Reply-To: <h46ds3$etn$1@ger.gmane.org>
Koen Kooi skrev:
> On 21-07-09 22:40, Ulf Samuelsson wrote:
>> Cliff Brake skrev:
[snip]
>> ERROR: Required build target 'gpe-image' has no buildable providers.
>> Missing or unbuildable dependency chain was: ['gpe-image',
>> 'task-gpe-base', 'bluez-utils-dbus', 'bluez-libs-3.36']
>> -----------------------------
>>
>> Do we want to disable bluetooth in Angstrom, until this is fixed,
>> or is it just gpe-image that has a problem with bluetooth?
>
> A few things:
>
> 1) don't use gpe-image with angstrom, but x11-image or x11-gpe-image
OK, The Wiki gives "gpe-image" and "opie-image" as examples.
I changed "gpe-image" to "x11-gpe-image" and added "x11-image"
> 2)
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=165ddf1987723725ab49189a3533b8ae65100bfa
>
> 3) No, don't disable bluetooth in angstrom when some crufty old recipe
> depends on stuff we removed years ago from OE.
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2009-07-22 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 16:00 OE weekly changelog 2009-07-13 to 2009-07-20 Cliff Brake
2009-07-21 20:40 ` OE weekly changelog 2009-07-13 to 2009-07-20 - Bluetooth still not working Ulf Samuelsson
2009-07-22 7:07 ` Koen Kooi
2009-07-22 9:42 ` Ulf Samuelsson [this message]
2009-07-22 10:31 ` Koen Kooi
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=4A66DF13.2030907@atmel.com \
--to=ulf.samuelsson@atmel.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.