public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez3.30 audio/serial plugin issue
Date: Tue, 15 Apr 2008 20:07:37 +0200	[thread overview]
Message-ID: <4804EEE9.4030500@suse.de> (raw)
In-Reply-To: <0D66FC67-0CE2-4BFD-BA90-4627158FD98D@holtmann.org>

Marcel Holtmann schrieb:
> I would like to ignore it, but I can't. Can you do a ls -la inside the
> installed plugins directory. Maybe libtool is messing this up. Or

seife@stoetzler:~> ls -la /usr/lib64/bluetooth/plugins/
total 204
drwxr-xr-x 2 root root  4096 10. Apr 14:07 .
drwxr-xr-x 3 root root  4096  9. Apr 07:09 ..
-rw-r--r-- 1 root root   794  9. Apr 07:09 libinput.la
-rwxr-xr-x 1 root root 53680  9. Apr 07:09 libinput.so
-rw-r--r-- 1 root root   806  9. Apr 07:09 libnetwork.la
-rwxr-xr-x 1 root root 58896  9. Apr 07:09 libnetwork.so
-rw-r--r-- 1 root root   800  9. Apr 07:09 libserial.la
-rwxr-xr-x 1 root root 53888  9. Apr 07:09 libserial.so

then i built a package without "--enable-glib", and i removed the .la files:
seife@stoetzler:~> ls -la /usr/lib64/bluetooth/plugins/
total 220
drwxr-xr-x 2 root root  4096 15. Apr 20:03 .
drwxr-xr-x 3 root root  4096 15. Apr 20:01 ..
-rwxr-xr-x 1 root root 64758 15. Apr 20:01 libinput.so
-rwxr-xr-x 1 root root 71327 15. Apr 20:01 libnetwork.so
-rwxr-xr-x 1 root root 65302 15. Apr 20:01 libserial.so

alas, it does not work:
Apr 15 20:03:26 stoetzler hcid[27467]: Device hci0 has been activated
Apr 15 20:03:26 stoetzler hcid[27467]: Starting SDP server
Apr 15 20:03:26 stoetzler hcid[27467]: Can't load plugin:
/usr/lib64/bluetooth/plugins/libnetwork.so: invalid mode for dlopen(): Inva=
lid
argument
Apr 15 20:03:26 stoetzler hcid[27467]: Can't load plugin:
/usr/lib64/bluetooth/plugins/libserial.so: invalid mode for dlopen(): Inval=
id
argument
Apr 15 20:03:26 stoetzler hcid[27467]: Can't load plugin:
/usr/lib64/bluetooth/plugins/libinput.so: invalid mode for dlopen(): Invalid
argument

-- =

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)

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference =

Don't miss this year's exciting event. There's still time to save $100. =

Use priority code J8TL2D2. =

http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java=
one
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-04-15 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  8:33 [Bluez-users] bluez3.30 audio/serial plugin issue dong yan
2008-04-11  8:44 ` Marcel Holtmann
2008-04-12 10:13   ` Stefan Seyfried
2008-04-12 20:02     ` Marcel Holtmann
2008-04-15 18:07       ` Stefan Seyfried [this message]
2008-04-15  3:26   ` dong yan
  -- strict thread matches above, loose matches on Subject: below --
2008-04-14 11:13 Jimmi

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=4804EEE9.4030500@suse.de \
    --to=seife@suse.de \
    --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