From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Loading plugin error
Date: Fri, 4 Apr 2008 20:37:45 +0200 [thread overview]
Message-ID: <B7288477-95BD-40EB-BC12-F78457376787@holtmann.org> (raw)
In-Reply-To: <20080404173913.GA27374@suse.de>
Hi Stefan,
>>
>>
>> (enable-all should IIUC include enable-glib, but i used it anyway,
>> it did not
>> change anything)
>
> This still applies: i gave "--enable-all" and this should, according
> to the
> configure --help output also enable glib:
> ...
> --enable-all enable all extra options below
> --enable-inotify enable inotify support
> --enable-hal enable HAL support
> --enable-usb enable USB support
> --enable-alsa enable ALSA support
> --enable-glib enable GLib support
> --enable-gstreamer enable GStreamer support
> ...
>
> But it didn't.
> Also, IMHO we should refuse to build the plugins if glib is not
> enabled.
> Unfortunately i know next to nothing about auto$foo, so i have no
> patch
> handy :-(
it should work with eglib. That is actually a bug if it doesn't. Not
that I care much since eglib is going away with 4.0, but it is a bug
within 3.x series.
Regards
Marcel
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2008-04-04 18:37 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
2008-04-04 17:39 ` Stefan Seyfried
2008-04-04 18:37 ` Marcel Holtmann [this message]
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=B7288477-95BD-40EB-BC12-F78457376787@holtmann.org \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox