Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031379AbbD2QrQ (ORCPT ); Wed, 29 Apr 2015 12:47:16 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:36355 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965755AbbD2QrM (ORCPT ); Wed, 29 Apr 2015 12:47:12 -0400 MIME-Version: 1.0 In-Reply-To: References: <1430322871-18107-1-git-send-email-namhyung@kernel.org> <20150429160233.GA8427@krava.redhat.com> Date: Wed, 29 Apr 2015 13:47:11 -0300 Message-ID: Subject: Re: [PATCH] perf tools: Fix bison-related build failure on CentOS 6 From: Arnaldo Carvalho de Melo To: Namhyung Kim Cc: Jiri Olsa , Arnaldo Carvalho de Melo , Ingo Molnar , Peter Zijlstra , LKML , David Ahern Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1198 Lines: 26 On Wed, Apr 29, 2015 at 1:11 PM, Namhyung Kim wrote: > On Thu, Apr 30, 2015 at 1:02 AM, Jiri Olsa 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/