[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+JHD91O3O14mYijyJAsH4ajC4gJH_w61fYuttF5k9JHnUowXQ@mail.gmail.com>
Date: Wed, 29 Apr 2015 13:47:11 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Jiri Olsa <jolsa@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>
Subject: Re: [PATCH] perf tools: Fix bison-related build failure on CentOS 6
On Wed, Apr 29, 2015 at 1:11 PM, Namhyung Kim <namhyung@...nel.org> wrote:
> On Thu, Apr 30, 2015 at 1:02 AM, Jiri Olsa <jolsa@...hat.com> wrote:
>> On Thu, Apr 30, 2015 at 12:54:31AM +0900, Namhyung Kim wrote:
>>> The YYLTYPE_IS_TRIVIAL is defined in the Build file, but unlike
>>> pmu-bison.c, gcc complained about it for parse-events-bison.c:
>>
>> any clue why is that? cant see why Fedora is not complaining
>> over the same sources and RHEL6 fails..
>
> I have no idea. I just found it during build test using containers,
> and had no chance to look into the bison code..
Well, applied tested it on both rhel7, fedora21 and rhel6.6, seems to work,
have it in my perf/core branch at git.kernel.org, that branch now builds on
rhel6.6, after fixing issues with several patches that were making it shadow
some functions (util.h's error(), etc).
If we can get a better message for that, figuring out what that
_IS_TRIVIAL thingy does....
- Arnaldo
--
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