From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752005AbcEFE6O (ORCPT ); Fri, 6 May 2016 00:58:14 -0400 Received: from ozlabs.org ([103.22.144.67]:48704 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750915AbcEFE6N (ORCPT ); Fri, 6 May 2016 00:58:13 -0400 Date: Fri, 6 May 2016 14:58:10 +1000 From: Stephen Rothwell To: Andrew Morton Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Arnd Bergmann Subject: linux-next: build failure after merge of the akpm-current tree Message-ID: <20160506145810.04a319d3@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 Andrew, After merging the akpm-current tree, today's linux-next build (and a few earlier ones) (powerpc allnoconfig (and many others)) failed like this: lib/vsprintf.c:160:2: error: initializer element is not constant lib/vsprintf.c:160:2: error: (near initialization for 'decpair[0]') lib/vsprintf.c:160:2: error: initializer element is not constant lib/vsprintf.c:160:2: error: (near initialization for 'decpair[1]') lib/vsprintf.c:160:2: error: initializer element is not constant lib/vsprintf.c:160:2: error: (near initialization for 'decpair[2]') lib/vsprintf.c:160:2: error: initializer element is not constant lib/vsprintf.c:160:2: error: (near initialization for 'decpair[3]') lib/vsprintf.c:160:2: error: initializer element is not constant and more ... basically any big endian build of code using __swabxx or cpu_to_lexx in initailisers (in the above case cpu_to_le16()). Caused (presumably) by commit eeee46ed3cda ("byteswap: try to avoid __builtin_constant_p gcc bug") This is a buyild using gcc 4.6.3. I have revreted that commit for today to see if it fixes the overnight builds. -- Cheers, Stephen Rothwell