From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Re: compile problem with bluez-utils-2.23 (uint16_t, .. missing)
Date: Tue, 20 Dec 2005 00:00:04 +0100 [thread overview]
Message-ID: <1135033204.5236.4.camel@localhost> (raw)
In-Reply-To: <m3acewyaat.fsf@gondor.middle-earth.priv>
Hi Christian,
> > > I've tried to compile bluez-utils 2.23 and it failed with an error:
> > >
> > > if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../common -I/usr/include -I/usr/include -O2
> >-fomit-frame-pointer -pipe -march=i586 -mtune=athlon -D_FORTIFY_SOURCE=2 -MT csr_usb.o -MD
> >-MP -MF ".deps/csr_usb.Tpo" -c -o csr_usb.o csr_usb.c; \
> > > then mv -f ".deps/csr_usb.Tpo" ".deps/csr_usb.Po"; else rm -f ".deps/csr_usb.Tpo"; exit
> >1; fi
> > > In file included from csr_usb.c:34:
> > > csr.h:500: error: syntax error before "def"
> > > csr.h:501: error: syntax error before "id"
> > > csr.h:502: error: syntax error before "ver"
> > > csr.h:503: error: syntax error before "pskey"
> > > csr.h:504: error: syntax error before "pskey"
> > > csr.h:507: error: syntax error before "varid"
> > > csr.h:508: error: syntax error before "varid"
> > > csr.h:512: error: syntax error before "varid"
> > > csr.h:513: error: syntax error before "varid"
> > > csr.h:517: error: syntax error before "varid"
> > > csr.h:518: error: syntax error before "varid"
> > >
> > > It seems, that uint16_t, uint32_t, ... are not found.
> >
> > what compiler do you use? I never had that problem.
>
> $ gcc --version
> gcc-bin (GCC) 3.4.5
I bascially moved to GCC 4.x as default compiler and it seems there are
some headers included by default, but you also got more warning as
before.
> > > I've solved the problem by including inttypes.h in csr.h:
> >
> > I prefer using <stdint.h>. Does this also work for you?
>
> Yes, including stdint.h works as well.
It's already in the CVS. Thanks.
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-12-19 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 22:46 [Bluez-devel] Re: Re: compile problem with bluez-utils-2.23 (uint16_t, .. missing) Christian Krause
2005-12-19 23:00 ` Marcel Holtmann [this message]
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=1135033204.5236.4.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).