From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Build problem with plugz
Date: Mon, 15 Jan 2007 19:37:03 -0700 [thread overview]
Message-ID: <45AC3A4F.7030408@xmission.com> (raw)
In-Reply-To: <7ff566830701151639u5d62348dx4042e23361f028b1@mail.gmail.com>
Kelly
I think you'll need newer bluez libraries & dev packages.
Brad
> I'm having a problem compiling plugz:
>
> gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -O2 -MT states.o -MD -MP -MF
> .deps/states.Tpo -c -o states.o states.c
> states.c: In function 'headsetIdleHandleApplConnReq':
> states.c:300: error: 'SDP_NON_BLOCKING' undeclared (first use in this function)
> states.c:300: error: (Each undeclared identifier is reported only once
> states.c:300: error: for each function it appears in.)
> make[3]: *** [states.o] Error 1
>
> This was after the CVS pull. I'm building on Gentoo, kernel 2.6.19.2.
>
-------------------------------------------------------------------------
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-16 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 0:39 [Bluez-devel] Build problem with plugz Kelly Price
2007-01-16 2:37 ` Brad Midgley [this message]
2007-01-16 21:14 ` Kelly Price
2007-01-17 4:55 ` Brad Midgley
2007-01-17 11:23 ` Kelly Price
2007-01-17 14:56 ` Robert Huitl
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=45AC3A4F.7030408@xmission.com \
--to=bmidgley@xmission.com \
--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