From: Marcel Holtmann <marcel@holtmann.org>
To: David Stockwell <dstockwell@frequency-one.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Problems building lexer.c in rfcomm
Date: Tue, 09 Jun 2009 17:23:13 +0200 [thread overview]
Message-ID: <1244560993.3068.15.camel@localhost.localdomain> (raw)
In-Reply-To: <C8BAD89E00F6479FBCA47D5EB8A39A98@freqonedev>
Hi David,
> I am working in audio/control.c, and cannot "make" bluez 4.40 (plus my
> changes, all in audio/control.c).
>
> The make is failing when building rfcomm/lexer.c:
>
> cc1: warnings being treated as errors
> lexer.c: In function 'yy_get_next_buffer'
> lexer.c:1095: error: comparison between signed and unsigned
>
> Has anyone else seen this error? How did you deal with it or work
> around it?
it is a compiler warning and should be fixed with newer Bison versions.
I don't see that one anymore.
Regards
Marcel
prev parent reply other threads:[~2009-06-09 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 14:30 Problems building lexer.c in rfcomm David Stockwell
2009-06-09 15:23 ` 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=1244560993.3068.15.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=dstockwell@frequency-one.com \
--cc=linux-bluetooth@vger.kernel.org \
/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