From: Roger Barnes <roger@mindsocket.com.au>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Compilation Problem Plugz
Date: Tue, 9 Jan 2007 09:27:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20070109T102250-819@post.gmane.org> (raw)
In-Reply-To: 459BCF21.5020005@xmission.com
> > a2dpd_dbus.c:31:28: error: dbus/dbus-glib.h: No such file or directory
> > a2dpd_dbus.c:32:37: error: dbus/dbus-glib-lowlevel.h: No such file or
> > directory
>
> you will need to install libdbus-1-dev and libdbus-glib-1-dev. I just
> updated the build docs with these.
>
> Brad
>
I'm experiencing the same problem here, and have these packages installed
(Ubuntu edgy). The problem appears to be blank DBUS_CFLAGS in the compile. My
Makefile contains:
DBUS_CFLAGS = -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
But the make output shows blanks:
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/include -pthread -Wall -O2 -c
a2dpd_dbus.c
a2dpd_dbus.c:31:28: error: dbus/dbus-glib.h: No such file or directory
a2dpd_dbus.c:32:37: error: dbus/dbus-glib-lowlevel.h: No such file or directory
Manually running gcc with the gap filled in worked and got me past this.
Cheers,
- Roger
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-09 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 14:44 [Bluez-devel] Compilation Problem Plugz Tom Lloyd
2007-01-03 15:16 ` Frédéric DALLEAU
2007-01-03 15:43 ` Brad Midgley
2007-01-09 9:27 ` Roger Barnes [this message]
2007-01-11 6:47 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 19:07 Steve Romanow
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=loom.20070109T102250-819@post.gmane.org \
--to=roger@mindsocket.com.au \
--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