On Fri, May 20, 2016 at 09:34:20AM +0300, Nikolay Borisov wrote: > > > On 05/20/2016 09:28 AM, Greg KH wrote: > > On Fri, May 20, 2016 at 09:19:04AM +0300, Nikolay Borisov wrote: > >> > >> > >> On 05/19/2016 06:33 PM, Greg KH wrote: > >>> On Thu, May 19, 2016 at 06:00:30PM +0300, Nikolay Borisov wrote: > >>>> [Resending since I did mistyped the stable mailing list address] > >>>> > >>>>> On Wed, May 18, 2016 at 06:13:43PM +0300, Nikolay Borisov wrote: > >>>>>> > >>>>>> > >>>>>> On 05/18/2016 06:10 PM, Greg KH wrote: > >>>>>>> On Wed, May 18, 2016 at 04:02:35PM +0300, Nikolay Borisov wrote: > >>>>>>>> Hello Greg, > >>>>>>>> > >>>>>>>> Turns out building perf is broken in the 4.4 kernel tree on centos6. > >>>>>>>> Executing make in toosl/perf results in : > >>>>>>>> > >>>>>>>> cc1: warnings being treated as errors > >>>>>>>> tests/llvm.c: In function ‘test_llvm__fetch_bpf_obj’: > >>>>>>>> tests/llvm.c:53: error: declaration of ‘index’ shadows a global declaration > >>>>>>>> /usr/include/string.h:489: error: shadowed declaration is here > >>>>>>>> mv: cannot stat `tests/.llvm.o.tmp': No such file or directory > >>>>>>>> > >>>>>>>> This can be fixed by applying the following commit: > >>>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=916d4092a1d2d7bb50630497be71ee4c4c2807fa > >>>>>>>> > >>>>>>>> Would it be possible to apply it for 4.4.12 otherwise using perf from > >>>>>>>> that tree is useless? > >>>>>>> > >>>>>>> Is this something that recently broke? Or has it always been an issue? > >>>>>> > >>>>>> According to the Fixes tags in the commit this broke in the following > >>>>>> series: http://marc.info/?l=linux-kernel&m=144681782820358 > >>>>>> > >>>>>> Which was applied in November 6. 2015. So I'd say it's been fairly > >>>>>> recently. > >>>>> > >>>>> So it's always been broken in 4.4? Or did I break it in a newer > >>>>> release? > >>>> > >>>> Before that I was on 3.12 stable and everything worked, so I guess it > >>>> did break in the release which included the aforementioned patches. > >>> > >>> That's not what I need to know. Is 4.4.0 broken? If not, then I worry, > >>> if so, then there's not really anything interesting here. Unless 4.6.0 > >>> also works. Does it? > >> > >> Just tested, so 4.4.0 is broken, 4.6 works. > > > > Great, can you use 'git bisect' to find the patch that fixes it? > > Well, I have given you a link to this patch in my first email. I can't > understand what the problem here is ? Doh, sorry, you are correct, I got confused here, thanks for being persistent... greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html