From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755463AbcDNMf5 (ORCPT ); Thu, 14 Apr 2016 08:35:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43223 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755443AbcDNMfz (ORCPT ); Thu, 14 Apr 2016 08:35:55 -0400 Date: Thu, 14 Apr 2016 09:35:52 -0300 From: Arnaldo Carvalho de Melo To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the tip tree Message-ID: <20160414123552.GD2439@redhat.com> References: <20160414121418.288bd117@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160414121418.288bd117@canb.auug.org.au> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.20 (2009-12-10) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Thu, 14 Apr 2016 12:35:54 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc64le perf) > failed like this: > > make[3]: *** No rule to make target '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by '/home/sfr/next/perf/util/syscalltbl.o'. Stop. > > (I build in /home/sfr/next/next with objects in /home/sfr/next/perf.) I'll check, should've been caught by a cross compiler build for ppc64le I have in place :-\ minimal-ubuntu-x-ppc64el: Ok But maybe not, as this requires audit-libs-devel and that is not present on that minimal ubuntu x-compiler setup, sigh :-\ - Arnaldo > Presumably caused by commit > > 1b700c997500 ("perf tools: Build syscall table .c header from kernel's syscall_64.tbl") > > I have reverted that commit for today (which fixes my build problem but > may not be overall correct). > > -- > Cheers, > Stephen Rothwell