Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756124AbZFVJje (ORCPT ); Mon, 22 Jun 2009 05:39:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755180AbZFVJj0 (ORCPT ); Mon, 22 Jun 2009 05:39:26 -0400 Received: from pfepb.post.tele.dk ([195.41.46.236]:42712 "EHLO pfepb.post.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755167AbZFVJjZ (ORCPT ); Mon, 22 Jun 2009 05:39:25 -0400 Date: Mon, 22 Jun 2009 11:41:43 +0200 From: Sam Ravnborg To: Stephen Rothwell Cc: Linus , LKML , ppc-dev , Andrew Morton , James Simmons , Krzysztof Helt , Geert Uytterhoeven Subject: Re: [PATCH] fbdev: work around old compiler bug Message-ID: <20090622094143.GA8121@uranus.ravnborg.org> References: <20090622180420.2e0424e4.sfr@canb.auug.org.au> <20090622183415.46fa786b.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090622183415.46fa786b.sfr@canb.auug.org.au> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 977 Lines: 26 On Mon, Jun 22, 2009 at 06:34:15PM +1000, Stephen Rothwell wrote: > On Mon, 22 Jun 2009 18:04:20 +1000 Stephen Rothwell wrote: > > > > When building with a 4.1.x compiler on powerpc64 (at least) we get > > this error: > > Ignore this, it causes more problems: > > drivers/video/logo/logo_linux_clut224.c:548: error: logo_linux_clut224_clut causes a section type conflict > > I'll work on a better solution. I have no time to experiemnt atm. But I have seen this before. It happens when we mix up const and non-const stuff. I would assume the simple solution is to replace _initconst with _initdata for all users. If you get it to work with powerpc then it works for everyone (or so it is usually). Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/