From: neoclust <neoclust@mandriva.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] can't build bluez-utils 2.21
Date: Tue, 4 Oct 2005 21:18:52 +0200 [thread overview]
Message-ID: <200510042118.53657.neoclust@mandriva.org> (raw)
hi,
i can't build bluez-utils 2.21, i obtain this error:
In file included from csrinit.c:40:
csr.h:76: error: syntax error before 'id'
csr.h:77: error: syntax error before 'ver'
csr.h:78: error: syntax error before 'pskey'
csr.h:80: error: syntax error before 'uint16_t'
csr.h:81: error: syntax error before 'uint16_t'
csr.h:82: error: syntax error before 'uint16_t'
csr.h:83: error: syntax error before 'uint16_t'
csr.h:84: error: syntax error before 'uint16_t'
csr.h:85: error: syntax error before 'uint16_t'
csr.h:86: error: syntax error before 'uint16_t'
ICECREAM[16465]: Compiled on 192.168.2.53
make[2]: *** [csrinit.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mkdir .libs
gcc -I/usr/include -I/usr/include -O2 -pipe -Wp,-D_FORTIFY_SOURCE=2
-fomit-frame-pointer -march=i586 -mtune=pentiumpro -fpic -o hcitool hcitool.o
oui.o -L/usr/lib /lib/libbluetooth.so ../common/libtextfile.a
make[2]: Leaving directory `/home/neoclust/rpm/BUILD/bluez-utils-2.21/tools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/neoclust/rpm/BUILD/bluez-utils-2.21'
make: *** [all] Error 2
I have bluez-lib 2.21
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-10-04 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 19:18 neoclust [this message]
2005-10-04 19:56 ` [Bluez-users] can't build bluez-utils 2.21 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=200510042118.53657.neoclust@mandriva.org \
--to=neoclust@mandriva.org \
--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;
as well as URLs for NNTP newsgroup(s).