From: "leiyu" <leiyu@kcoe.cn>
To: "Bluez-Users" <bluez-users@lists.sourceforge.net>,
"sumeet" <sumeet.verma@st.com>
Subject: [Bluez-users] RE: [Bluez-users]RE￡ocross-compile bluez-utils-3.9
Date: Wed, 25 Jul 2007 14:46:43 +0800 [thread overview]
Message-ID: <EJENLMBEOLKAMCJFBFMDGEDNCAAA.leiyu@kcoe.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
Dear Sumeet,
I add the option --includedir and --libdir to the configure string
./configure --prefix=/bluez/bluez-uitls --host=arm-linux
--includedir=/bluez/bluez-libs/include --libdir=/bluez/bluez-libs/lib
but it have the same error
sdp-xml.c:36:27: bluetooth/sdp.h: no such file or directory
sdp-xml.c:37:31: bluetooth/sdp_lib.h: no such file or directory
it's very strange, I feel ashamed to bother you again , thank you very much
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 reply other threads:[~2007-07-25 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 6:46 leiyu [this message]
2007-07-25 7:03 ` [Bluez-users] RE: [Bluez-users]RE?êocross-compile bluez-utils-3.9 Sumeet VERMA
-- strict thread matches above, loose matches on Subject: below --
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
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=EJENLMBEOLKAMCJFBFMDGEDNCAAA.leiyu@kcoe.cn \
--to=leiyu@kcoe.cn \
--cc=bluez-users@lists.sourceforge.net \
--cc=sumeet.verma@st.com \
/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