Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757571Ab2EDDQU (ORCPT ); Thu, 3 May 2012 23:16:20 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:45899 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752817Ab2EDDQT (ORCPT ); Thu, 3 May 2012 23:16:19 -0400 Date: Thu, 3 May 2012 20:16:14 -0700 From: Greg KH To: Arnaud Lacombe Cc: David Miller , namhyung.kim@lge.com, a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com, acme@ghostprotocols.net, jolsa@redhat.com, linux-kernel@vger.kernel.org Subject: Re: perf build failure on Linus's tree Message-ID: <20120504031614.GA12048@kroah.com> References: <20120503215748.GA18995@kroah.com> <87sjfgafqj.fsf@sejong.aot.lge.com> <20120503.215020.954262287222794218.davem@davemloft.net> <20120504024706.GA10461@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1767 Lines: 42 On Thu, May 03, 2012 at 11:01:54PM -0400, Arnaud Lacombe wrote: > Hi, > > On Thu, May 3, 2012 at 10:47 PM, Greg KH wrote: > > On Thu, May 03, 2012 at 10:35:02PM -0400, Arnaud Lacombe wrote: > >> Hi, > >> > >> On Thu, May 3, 2012 at 10:29 PM, Arnaud Lacombe wrote: > >> > [...] > >> > [0]: http://pkgs.fedoraproject.org/gitweb/?p=flex.git;a=blob;f=flex-2.5.35-hardening.patch;h=7d608ea2371fa3295bdb8eb97c15eeb03029c02b;hb=HEAD > >> > > >> as a side note, this patch sounds more being about "silencing" than > >> "hardening"... > > > > That's nice, but I can build the perf version in 3.3 just fine, so > > something broke here (hint, build regression.) ?Do I have to bisect it > > down to find the problem? > > > there is most likely nothing to bisect, `perf' seems to have never > required any parser before 3.4. The way the rest of the tools > (especially `kconfig', `genksyms' and `dtc') manage parsers is via > pre-generated .[ch]_shipped version of the lexer/tokenizer. It's been > working well for a long time as such. `perf' will certainly have to > follow the same path. Well, it can allow bison to run, but just don't break the build if the generated code it creates happens to contain warnings. I'm using bison 2.5 and flex 2.5.35, and my phone number is... Like this really matters? This needs to work for everyone, if not, you better put the specific version numbers you need to require in the Documentation/Changes file. So, how do I fix this? greg k-h -- 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/