[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120615183503.GA27556@gmail.com>
Date: Fri, 15 Jun 2012 20:35:03 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...radead.org>
Cc: linux-kernel@...r.kernel.org,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
David Ahern <dsahern@...il.com>,
Dmitry Antipov <dmitry.antipov@...aro.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Jim Cromie <jim.cromie@...il.com>,
Jiri Olsa <jolsa@...hat.com>, Mike Galbraith <efault@....de>,
Namhyung Kim <namhyung@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <peterz@...radead.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [GIT PULL 0/3] perf/urgent fixes
The build does not want to fail anymore :-/
I have no idea what state my tree was in - but I re-applied your
patches and the failure happened again in 'make -j':
CC builtin-help.o
CC builtin-timechart.o
util/parse-events.l: In function ‘__value’:
util/parse-events.l:18:10: error: ‘PE_ERROR’ undeclared (first
use in this function)
util/parse-events.l:18:10: note: each undeclared identifier is
reported only once for each function it appears in
util/parse-events.l:20:2: error: ‘parse_events_lval’ undeclared
(first use in this function)
util/parse-events.l: In function ‘value’:
util/parse-events.l:26:42: error: ‘PE_VALUE’ undeclared (first
use in this function)
then I took off the last patch and did a 'make' - and the bug
did not re-trigger, even after applying your patches again.
It could be some sort of build dependency problem with the flex
files.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists