From: Marcel Holtmann <marcel@holtmann.org>
To: Tehyih D Wan <tdwan@MIT.EDU>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] installing bluez-hciemu-1.0 on Debian--GLib not found
Date: Sat, 17 Apr 2004 02:16:51 +0200 [thread overview]
Message-ID: <1082161011.4489.30.camel@pegasus> (raw)
In-Reply-To: <1081889721.407c53b90c5d4@webmail.mit.edu>
Hi Debbie,
> I'm trying to install bluez-hciemu on Debian, and getting the error "checking
> for glib-config...not found" when I run the ./configure script.
>
> I've installed libglib2.0, libglib2.0-dev, libglib2.0-data, and libglib2.0-dbg,
> but I still get the same error when running the ./configure script.
>
> There was a thread about this same problem back in 2003 but the only suggestion
> seemed to be to try installing the -dev packages for Glib. Any ideas on what
> else I might try?
change the source of hciemu to use Glib 2.x (and send us a patch) or
install the development packages of Glib 1.4.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-04-17 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 20:55 [Bluez-users] installing bluez-hciemu-1.0 on Debian--GLib not found Tehyih D Wan
2004-04-13 22:14 ` Michal Semler (volny.cz)
2004-04-17 0:16 ` Marcel Holtmann [this message]
2004-04-21 16:01 ` Tehyih D Wan
2004-04-21 16:35 ` 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=1082161011.4489.30.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=tdwan@MIT.EDU \
/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