From: Marcel Holtmann <marcel@holtmann.org>
To: nased0 <nased0@aster.pl>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez-utils-3.36 hidd daemon does not compile on Suse 11 x64
Date: Thu, 17 Jul 2008 14:18:20 +0200 [thread overview]
Message-ID: <1216297100.22564.24.camel@violet.holtmann.net> (raw)
In-Reply-To: <1059545251.20080712172856@aster.pl>
Hi,
> I downloaded old version 2.25 of bluez-utils, compiled and installed it, then
> compiled and installed v. 3.36 over 2.25 to be able to use my MS
> Bluetooth mouse.
> Suse 11 64-bit distribution does not have a hidd daemon file included,
> therefore its Bluetooth configurators only pretend to work.
> I think that Suse 11 x64 distro developers were not able to
> compile is also.
I have no idea what you are talking about. The hidd compiles just fine
and the reason why SuSE not includes it is that the input service
supersedes hidd.
Regards
Marcel
next prev parent reply other threads:[~2008-07-17 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 15:28 Bluez-utils-3.36 hidd daemon does not compile on Suse 11 x64 nased0
2008-07-17 12:18 ` Marcel Holtmann [this message]
2008-07-17 18:37 ` Stefan Seyfried
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 19:21 Pawel Witas
2008-07-20 14:41 ` Stefan Seyfried
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=1216297100.22564.24.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=nased0@aster.pl \
/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