From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932241AbcIUBMT (ORCPT ); Tue, 20 Sep 2016 21:12:19 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:46944 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755281AbcIUBMQ (ORCPT ); Tue, 20 Sep 2016 21:12:16 -0400 From: Thiago Jung Bauermann To: Michael Ellerman Cc: Stephen Rothwell , Andrew Morton , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the akpm-current tree Date: Tue, 20 Sep 2016 22:12:07 -0300 User-Agent: KMail/4.14.3 (Linux/4.4.0-36-generic; KDE/4.14.13; x86_64; ; ) In-Reply-To: <87bmzirta5.fsf@concordia.ellerman.id.au> References: <20160920164414.4062bb0b@canb.auug.org.au> <20160921091622.53067648@canb.auug.org.au> <87bmzirta5.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16092101-0024-0000-0000-0000010B7C59 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16092101-0025-0000-0000-000015BA876D Message-Id: <2398986.v4utNoeCOx@hactar> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-09-20_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609020000 definitions=main-1609210020 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 21 September 2016, 10:27:46 schrieb Michael Ellerman: > Stephen Rothwell writes: > > On Tue, 20 Sep 2016 22:00:32 +1000 Michael Ellerman wrote: > >> Ah yep looks like that's the problem, patch below should fix it? > > > > Yeah, I am just going to (logically) run "sed > > 's/CONFIG_WORD_SIZE/BITS/'" > > over the tree during the merge of the apm-current tree today. > > > >> I think I'd actually prefer it if purgatory didn't redefine the CFLAGS > >> from scratch, so I'll see if Thiago can do that and send a new version. > > > > That could be better, but there are still some additions of > > CONFIG_WORD_SIZE elsewhere :-( > > I don't see any others in yesterday's next? This kbuild failure is one case: https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-September/148898.html elf_util_64.o is only built if CONFIG_WORD_SIZE=64. This is affects the bisectabilty of many patches in the kexec_file_load series. Should I post a new version rebased on powerpc/next? -- []'s Thiago Jung Bauermann IBM Linux Technology Center