From: "shy" <shyboysby@hotmail.com>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] bluez utils complie error
Date: Thu, 17 Jan 2008 09:09:38 +0800 [thread overview]
Message-ID: <BAY134-DS3C865C476D02281CDD6BAB1410@phx.gbl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 855 bytes --]
hi, all
I encountered an error when I compiled the bluez utils. If I compiled the
original code without modifying any code, there would be no error. But If I
modified the code, e.g., I added "printf("test\n");" in the function
dev_info in hcitool.c, there would be an error:
make[2]: Entering directory
`/home/tester/bluez_code3.20/bluez-utils-3.20/hcid'
test -f parser.c || /bin/bash ../ylwrap parser.y y.tab.c parser.c y.tab.h
parser.h y.output parser.output -- yacc -d
../ylwrap: line 111: yacc: command not found
make[2]: *** [parser.c] Error 1
make[2]: Leaving directory
`/home/tester/bluez_code3.20/bluez-utils-3.20/hcid'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tester/bluez_code3.20/bluez-utils-3.20'
make: *** [all] Error 2
Could anyone help to resolve it?
Many thanks in advance.
Best regards
Shi Buyun
[-- Attachment #1.2: Type: text/html, Size: 1220 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-01-17 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 1:09 shy [this message]
2008-01-17 1:19 ` [Bluez-devel] bluez utils complie error Tim Hentenaar
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=BAY134-DS3C865C476D02281CDD6BAB1410@phx.gbl \
--to=shyboysby@hotmail.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