Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754856AbZALLSt (ORCPT ); Mon, 12 Jan 2009 06:18:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752186AbZALLSl (ORCPT ); Mon, 12 Jan 2009 06:18:41 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:52921 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751776AbZALLSk (ORCPT ); Mon, 12 Jan 2009 06:18:40 -0500 Date: Mon, 12 Jan 2009 12:18:27 +0100 From: Ingo Molnar To: Jiri Kosina Cc: Jeremy Fitzhardinge , linux-kernel@vger.kernel.org, Jaswinder Singh Rajput , "H. Peter Anvin" , Thomas Gleixner Subject: Re: build breakage -- paravirt_{alloc,free}_ldt Message-ID: <20090112111827.GB18265@elte.hu> References: <20090112105202.GF10405@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1433 Lines: 34 * Jiri Kosina wrote: > On Mon, 12 Jan 2009, Ingo Molnar wrote: > > > > with Linus' tree (ae04d14015) doesn't build for me with > > > > > > arch/x86/kernel/ldt.c: In function 'alloc_ldt': > > > arch/x86/kernel/ldt.c:55: error: implicit declaration of function 'paravirt_alloc_ldt' > > > arch/x86/kernel/ldt.c:79: error: implicit declaration of function 'paravirt_free_ldt' > > > > > > Config on http://www.jikos.cz/jikos/junk/.config > > > > hm, it builds fine here with your config. Did .28 build fine for you? The > > only change to this file since .28 has been Jaswinder's "423a540: x86: > > ldt.c fix style problems". > > Puzzled. On one system, I still get this build error even after make > mrpoper (I use this machine to build kernel routinely, so it certainly > didn't happen a few days ago). > > But I just tried on different system, and there is builds flawlessly. > It's gcc 4.3.1 vs 4.3.2. I will check a little bit more. beyond mrproper you might want to try 'git checkout HEAD . -f' as well, to get a forced checkout of the current working tree. Should there be any corruption in any of the source code files this will get rid of it. Ingo -- 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/