From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluez is uncompilable
Date: Sun, 22 Jan 2006 03:49:57 +0100 [thread overview]
Message-ID: <1137898197.20856.154.camel@localhost> (raw)
In-Reply-To: <200601220328.00979.mlipocky@atlas.sk>
Hi Martin,
> I now downloaded the latest bluez and I cannot compile the stuff, no matter
> what version of gcc I try. There must be a complete mess in the code.
>
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../common -I/usr/include -I/usr/include
> -Wall -O2 -D_FORTIFY_SOURCE=2 -c `test -f 'sdptool.c' || echo './'`sdptool.c
> sdptool.c: In function `print_raw_data':
> sdptool.c:590: warning: unknown conversion type character `j' in format
> sdptool.c:590: warning: too many arguments for format
> sdptool.c:605: warning: unknown conversion type character `j' in format
> sdptool.c:605: warning: too many arguments for format
> sdptool.c: In function `add_isync':
> sdptool.c:2621: `APPLE_AGENT_SVCLASS_ID' undeclared (first use in this
> function)
> sdptool.c:2621: (Each undeclared identifier is reported only once
> sdptool.c:2621: for each function it appears in.)
> sdptool.c: At top level:
> sdptool.c:2681: `APPLE_AGENT_SVCLASS_ID' undeclared here (not in a function)
> sdptool.c:2681: initializer element is not constant
> sdptool.c:2681: (near initialization for `service[30].class')
> make[2]: *** [sdptool.o] Error 1
> make[2]: Leaving directory
> `/home/mlipocky/install/synce/bluez-utils-2.25/tools'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/mlipocky/install/synce/bluez-utils-2.25'
> make: *** [all] Error 2
read the README and you will see that you need bluez-libs-2.25 in order
to compile bluez-utils-2.25.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-22 2:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 2:28 [Bluez-devel] bluez is uncompilable Martin Lipocky
2006-01-22 2:49 ` Marcel Holtmann [this message]
2006-01-22 10:20 ` Martin Lipocky
2006-01-22 11:37 ` Marcel Holtmann
2006-01-22 11:43 ` Martin Lipocky
2006-01-22 11:50 ` 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=1137898197.20856.154.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).