From: Julien Boibessot <julien.boibessot@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] bluez
Date: Sun, 28 Jun 2009 19:31:32 +0200 [thread overview]
Message-ID: <4A47A8F4.7060403@free.fr> (raw)
In-Reply-To: <8CF9D79FB605004381900048F6005988032DFBEB90@mucse405.eu.infineon.com>
Hi,
I know this topic is quite old but:
Nick.Thompson at infineon.com a ?crit :
> I have attached a patch to the bug system at http://busybox.net/bugs/view.php?id=6134 to add bluez-libs and bluez-utils version 3.36 to buildroot.
>
> Please make sure you use the latest patch as the first had an error in it which causes a build failure on release 0.9.29 uClibc platforms (the patch is not required in the latest 0.9.30-RC3 snapshots.)
>
Do somebody know where this bug report has gone ??
(I finally get the hardware to test it ;-) )
Regards,
Julien
prev parent reply other threads:[~2009-06-28 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 14:12 [Buildroot] bluez Michel Benoit
2008-11-06 16:43 ` Thomas Petazzoni
2008-11-07 11:06 ` Julien Boibessot
2008-11-07 11:16 ` Nick.Thompson at infineon.com
2008-11-10 14:56 ` Matuschka, Sebastian
2008-11-10 15:10 ` Nick.Thompson at infineon.com
2008-11-13 10:09 ` Nick.Thompson at infineon.com
2009-06-28 17:31 ` Julien Boibessot [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=4A47A8F4.7060403@free.fr \
--to=julien.boibessot@free.fr \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox