From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] configure: error: dbus > 0.35 is requered
Date: Sat, 11 Aug 2007 20:15:12 +0200 [thread overview]
Message-ID: <1186856112.6698.31.camel@violet> (raw)
In-Reply-To: <525899.68874.qm@web58013.mail.re3.yahoo.com>
Hi,
> I am using bluez-utils-3.11 for ARM embedded linux.
> When hcid is buildt, it complains libdbus-1.so
>
> /usr/lib/libdbus-1.so: could not read symbols: File in
> wrong format.
>
> Because embedded linux kernel version is awalys behind
> the most recent released kernel.
the libdbus has nothing to do with the kernel version. However stop
whining about embedded kernel versions. Use the latest upstream kernel
and not some vendor crap.
> And I could not find old versions for bluez in
> www.bluez.org.
>
> What version of libdbus needed to match
> bluez-utils-3.13 or 11?
Use the D-Bus 1.0.x release.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-11 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.164992.1186500592.21973.bluez-users@lists.sourceforge.net>
2007-08-07 19:02 ` [Bluez-users] configure: error: dbus > 0.35 is requered hong zhang
2007-08-11 18:15 ` Marcel Holtmann [this message]
2007-08-07 7:51 Je Co
2007-08-07 8:04 ` Marcel Holtmann
2007-08-07 11:10 ` Je Co
2007-08-07 11:18 ` Adrian van Dongen
2007-08-07 19:34 ` Je Co
2007-08-11 18:16 ` Marcel Holtmann
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=1186856112.6698.31.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.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