From: Gustavo Padovan <padovan@profusion.mobi>
To: Mickael Chazaux <mickael.chazaux@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Compile failure
Date: Mon, 11 Jul 2011 11:37:34 -0300 [thread overview]
Message-ID: <20110711143734.GB2816@joana> (raw)
In-Reply-To: <CAAbSJMWHNbSV9r7Cw3+3NHoZMzWth3h1_GWrxDf9ANGA=cLnfQ@mail.gmail.com>
* Mickael Chazaux <mickael.chazaux@gmail.com> [2011-07-10 16:10:22 +0200]:
> git://git.kernel.org/pub/scm/bluetooth/bluez.git, branch master,
> commit c34e7956441 fails to build :
>
> CC tools/lexer.o
> cc1: warnings being treated as errors
> tools/lexer.c: In function ‘yy_get_next_buffer’:
> tools/lexer.c:1095: erreur: comparaison entre des expressions entières
> signée et non signée
> tools/lexer.c: In function ‘yy_init_buffer’:
> tools/lexer.c:1415: erreur: implicit declaration of function ‘isatty’
> make[1]: *** [tools/lexer.o] Erreur 1
Are you using gentoo? There is a bug in gentoo flex ebuild that cause this.
Gustavo
next prev parent reply other threads:[~2011-07-11 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 14:10 Compile failure Mickael Chazaux
2011-07-11 13:05 ` Lucas De Marchi
2011-07-11 14:37 ` Gustavo Padovan [this message]
2011-07-11 14:56 ` Mickael Chazaux
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=20110711143734.GB2816@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mickael.chazaux@gmail.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