All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhares <ml-sourceforge@stfw.eu>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dbus-glib problem
Date: Tue, 20 Jun 2006 09:07:04 +0100	[thread overview]
Message-ID: <4497ACA8.1030102@stfw.eu> (raw)
In-Reply-To: <1150787594.10957.5.camel@localhost>

Marcel Holtmann wrote:

>> checking for BLUEZ... yes
>> checking for DBUS... Package dbus-glib-1 was not found in the pkg-config search path.
>> Perhaps you should add the directory containing `dbus-glib-1.pc'
>> to the PKG_CONFIG_PATH environment variable
>> No package 'dbus-glib-1' found
>> configure: error: dbus-glib > 0.35 is required
>>
>> There seem to be some dependencies. I have tried installing dbus-0.61 and glib-2.8.6 but it does not work. Please tell me what packages to install to remove these dependencies and send me a link also if possible.
> 
> we don't require the dbus-glib bindings. No idea why it is looking for
> them. This seems like a bug in D-Bus package. What kind distribution is
> this?

Hi!
I had the same problem on my ubuntu. You have to install dbus-glib-dev. 
The configure script is looking for the include files but apparently 
does not seems to say it.

-- 

Zhares


_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2006-06-20  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  4:32 [Bluez-users] dbus-glib problem Sumeet VERMA
2006-06-20  7:13 ` Marcel Holtmann
2006-06-20  7:46   ` Sumeet VERMA
2006-06-20  8:02     ` Marcel Holtmann
2006-06-20  8:07   ` Zhares [this message]
2006-06-20  8:31     ` Marcel Holtmann
2006-06-21  5:22       ` Sumeet VERMA
2006-06-21  7:08         ` 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=4497ACA8.1030102@stfw.eu \
    --to=ml-sourceforge@stfw.eu \
    --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 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.