From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluez-utils-3.30 (patched) plugins failing at startup
Date: Tue, 29 Apr 2008 16:07:50 +0200 [thread overview]
Message-ID: <48172BB6.8040303@suse.de> (raw)
In-Reply-To: <012d01c8a8d3$4669be00$6701a8c0@freqonedev>
David Stockwell wrote:
> As stated in my last message, I caught up with all recent patches from hc=
id, and now find that when initializing the libxxxxx.so =
> plugins, the call to g_module_open STILL fails as shown in the following:
configure with "--enable-glib" (even if you did enable-all, this does not
enable glib) and that sould be it.
-- =
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-29 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 1:57 [Bluez-devel] Bluez-utils-3.30 (patched) plugins failing at startup David Stockwell
2008-04-29 14:07 ` Stefan Seyfried [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-29 22:31 David Stockwell
2008-04-29 22:35 David Stockwell
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=48172BB6.8040303@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.