From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Jiri Olsa <jolsa@redhat.com>, Arnaud Lacombe <lacombar@gmail.com>,
linux-kernel@vger.kernel.org
Subject: perf build failure on Linus's tree
Date: Thu, 3 May 2012 14:57:48 -0700 [thread overview]
Message-ID: <20120503215748.GA18995@kroah.com> (raw)
Linus's tree right now (3.4.rc5.67.gac001.dirty) gives me the following
build error when I try to build perf:
CC util/parse-events-flex.o
<stdout>: In function ‘yy_get_next_buffer’:
<stdout>:1510:3: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
util/parse-events.l: In function ‘parse_events_lex’:
util/parse-events.l:122:1: error: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result [-Werror=unused-result]
cc1: all warnings being treated as errors
Do you really want to ensure that flex's build warnings fail the build?
thanks,
greg k-h
next reply other threads:[~2012-05-03 21:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 21:57 Greg KH [this message]
2012-05-04 1:37 ` perf build failure on Linus's tree Namhyung Kim
2012-05-04 1:41 ` Greg KH
2012-05-04 1:45 ` Namhyung Kim
2012-05-04 1:50 ` David Miller
2012-05-04 2:14 ` Arnaud Lacombe
2012-05-04 2:24 ` Namhyung Kim
2012-05-04 2:29 ` Arnaud Lacombe
2012-05-04 2:35 ` Arnaud Lacombe
2012-05-04 2:47 ` Greg KH
2012-05-04 3:01 ` Arnaud Lacombe
2012-05-04 3:16 ` Greg KH
2012-05-04 4:01 ` Arnaud Lacombe
2012-05-04 7:09 ` [patch] perf: Fix build failure on OpenSuse userspace Ingo Molnar
2012-05-04 14:44 ` Arnaud Lacombe
2012-05-04 14:55 ` Namhyung Kim
2012-05-04 15:09 ` Greg KH
2012-05-04 15:02 ` Jiri Olsa
2012-05-04 15:26 ` Namhyung Kim
2012-05-04 15:03 ` Arnaldo Carvalho de Melo
2012-05-04 14:52 ` Greg KH
2012-05-04 15:10 ` Lucas De Marchi
2012-05-04 15:26 ` Jiri Olsa
2012-05-04 15:38 ` Namhyung Kim
2012-05-04 16:41 ` Jiri Olsa
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=20120503215748.GA18995@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.