From: "leiyu" <leiyu@kcoe.cn>
To: "Bluez-Users" <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Fail in cross-compile bluez-utils-3.9
Date: Tue, 24 Jul 2007 11:43:28 +0800 [thread overview]
Message-ID: <EJENLMBEOLKAMCJFBFMDAEDGCAAA.leiyu@kcoe.cn> (raw)
In-Reply-To: <EJENLMBEOLKAMCJFBFMDOEDDCAAA.leiyu@kcoe.cn>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1736 bytes --]
Dear ALL,
I has passed to configure bluez-utils by Sumeet's help.
But when I enter into bluez-utils directory then make it,
it happens many errors as below, How can I fix these problems?
Thanks very much for your help.
......
sdp-xml.c: In function `sdp_xml_parse_datatype':
sdp-xml.c:764: error: dereferencing pointer to incomplete type
sdp-xml.c:767: error: `SDP_BOOL' undeclared (first use in this function)
sdp-xml.c:769: error: `SDP_UINT8' undeclared (first use in this function)
sdp-xml.c:771: error: `SDP_UINT16' undeclared (first use in this function)
sdp-xml.c:773: error: `SDP_UINT32' undeclared (first use in this function)
sdp-xml.c:775: error: `SDP_UINT64' undeclared (first use in this function)
sdp-xml.c:777: error: `SDP_UINT128' undeclared (first use in this function)
sdp-xml.c:779: error: `SDP_INT8' undeclared (first use in this function)
sdp-xml.c:781: error: `SDP_INT16' undeclared (first use in this function)
sdp-xml.c:783: error: `SDP_INT32' undeclared (first use in this function)
sdp-xml.c:785: error: `SDP_INT64' undeclared (first use in this function)
sdp-xml.c:787: error: `SDP_INT128' undeclared (first use in this function)
sdp-xml.c:793: error: dereferencing pointer to incomplete type
sdp-xml.c: At top level:
sdp-xml.c:65: error: storage size of `indent' isn't known
sdp-xml.c:67: error: storage size of `next_indent' isn't known
sdp-xml.c:374: warning: `convert_raw_attr_to_xml_func' defined but not used
make[2]: *** [sdp-xml.o] error¯¯ 1
make[2]: Leaving directory `/bluez/bluez-3-3-2/bluez-utils-3.9/common'
make[1]: *** [all-recursive] error¯¯ 1
make[1]: Leaving directory `/bluez/bluez-3-3-2/bluez-utils-3.9'
make: *** [all] error¯¯ 2
Best regards,
Leiyu
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-07-24 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 7:56 [Bluez-users] Fail in cross-compile bluez-utils-3.9 leiyu
2007-07-20 8:16 ` Sumeet VERMA
2007-07-24 3:43 ` leiyu [this message]
2007-07-24 5:37 ` [Bluez-users] " leiyu
2007-07-25 4:21 ` [Bluez-users] RE:cross-compile bluez-utils-3.9 leiyu
2007-07-25 4:27 ` [Bluez-users] RE: [Bluez-users]RE£ocross-compile bluez-utils-3.9 Sumeet VERMA
2007-07-31 7:05 ` [Bluez-users] RE:cross-compile bluez-utils-3.9 leiyu
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=EJENLMBEOLKAMCJFBFMDAEDGCAAA.leiyu@kcoe.cn \
--to=leiyu@kcoe.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox