From: Stefan Seyfried <seife@suse.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Loading plugin error
Date: Fri, 4 Apr 2008 15:38:17 +0200 [thread overview]
Message-ID: <20080404133817.GA8298@suse.de> (raw)
In-Reply-To: <16c4cb990804040328i3af92a0x2db7d7297d323d31@mail.gmail.com>
On Fri, Apr 04, 2008 at 03:58:31PM +0530, rahul tank wrote:
> Ok .. i tried compiling bluez-utils with --enable-glib option and it solv=
ed
> the issue.
It did not for me.
I configured like this:
./configure --prefix=3D/usr \
--mandir=3D/usr/share/man \
--sysconfdir=3D/etc \
--libdir=3D/usr/lib \
--libexecdir=3D/lib \
--localstatedir=3D/var \
--enable-pie \
--enable-all --enable-glib
(enable-all should IIUC include enable-glib, but i used it anyway, it did n=
ot
change anything)
starting hcid with "-x -s" gives:
hcid[10053]: Bluetooth HCI daemon
hcid[10053]: HCI dev 0 registered
hcid[10053]: HCI dev 0 already up
hcid[10053]: Device hci0 has been added
hcid[10053]: Starting security manager 0
hcid[10053]: Device hci0 has been activated
hcid[10053]: Starting SDP server
hcid[10053]: Can't load plugin: /usr/lib/bluetooth/plugins/libaudio.so: inv=
alid mode for dlopen(): Invalid argument
hcid[10053]: Can't load plugin: /usr/lib/bluetooth/plugins/libserial.so: in=
valid mode for dlopen(): Invalid argument
hcid[10053]: Can't load plugin: /usr/lib/bluetooth/plugins/libnetwork.so: i=
nvalid mode for dlopen(): Invalid argument
hcid[10053]: Can't load plugin: /usr/lib/bluetooth/plugins/libinput.so: inv=
alid mode for dlopen(): Invalid argument
The plugins are available, unstripped etc:
seife@susi:~> file /usr/lib/bluetooth/plugins/*so
/usr/lib/bluetooth/plugins/libaudio.so: ELF 32-bit LSB shared object, Int=
el 80386, version 1 (SYSV), not stripped
/usr/lib/bluetooth/plugins/libinput.so: ELF 32-bit LSB shared object, Int=
el 80386, version 1 (SYSV), not stripped
/usr/lib/bluetooth/plugins/libnetwork.so: ELF 32-bit LSB shared object, Int=
el 80386, version 1 (SYSV), not stripped
/usr/lib/bluetooth/plugins/libserial.so: ELF 32-bit LSB shared object, Int=
el 80386, version 1 (SYSV), not stripped
Probably i'm doing something stupid, but i have no idea what ;-)
Thanks,
seife
-- =
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-04 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 8:52 [Bluez-devel] Loading plugin error rahul tank
2008-04-04 10:28 ` rahul tank
2008-04-04 13:38 ` Stefan Seyfried [this message]
2008-04-04 17:39 ` Stefan Seyfried
2008-04-04 18:37 ` 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=20080404133817.GA8298@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@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 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.