From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753306AbcITHaT (ORCPT ); Tue, 20 Sep 2016 03:30:19 -0400 Received: from ozlabs.org ([103.22.144.67]:54092 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751297AbcITHaP (ORCPT ); Tue, 20 Sep 2016 03:30:15 -0400 Date: Tue, 20 Sep 2016 17:30:12 +1000 From: Stephen Rothwell To: Andrew Morton Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Michael Ellerman Subject: Re: linux-next: build failure after merge of the akpm-current tree Message-ID: <20160920173012.1abe1d84@canb.auug.org.au> In-Reply-To: <20160920164414.4062bb0b@canb.auug.org.au> References: <20160920164414.4062bb0b@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, On Tue, 20 Sep 2016 16:44:14 +1000 Stephen Rothwell wrote: > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > powerpc-linux-gcc: error: unrecognized command line option '-m' > scripts/Makefile.build:290: recipe for target 'arch/powerpc/purgatory/printf.o' failed > > and a few more like that. OK, this is (most likely) caused by the CONFIG_WORD_SIZE -> BITS change interacting with the KEXEC_FILE changes. Tomorrow I will do a better merge conflict resolution patch that fixes all those. -- Cheers, Stephen Rothwell