Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263069AbTIGFgd (ORCPT ); Sun, 7 Sep 2003 01:36:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263070AbTIGFgd (ORCPT ); Sun, 7 Sep 2003 01:36:33 -0400 Received: from pasmtp.tele.dk ([193.162.159.95]:1540 "EHLO pasmtp.tele.dk") by vger.kernel.org with ESMTP id S263069AbTIGFgc (ORCPT ); Sun, 7 Sep 2003 01:36:32 -0400 Date: Sun, 7 Sep 2003 07:36:31 +0200 From: Sam Ravnborg To: Andi Kleen Cc: "Randy.Dunlap" , linux-kernel@vger.kernel.org Subject: Re: 2.6: spurious recompiles Message-ID: <20030907053631.GB963@mars.ravnborg.org> Mail-Followup-To: Andi Kleen , "Randy.Dunlap" , linux-kernel@vger.kernel.org References: <20030906201417.GI14436@fs.tum.de.suse.lists.linux.kernel> <33384.4.4.25.4.1062887601.squirrel@www.osdl.org.suse.lists.linux.kernel> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1004 Lines: 22 On Sun, Sep 07, 2003 at 12:44:24AM +0200, Andi Kleen wrote: > "Randy.Dunlap" writes: > > x86-64 has the same problem. It always rebuilds arch/x86_64/ia32/vsyscall32.so, > no matter if it has changed or not. I have not figured out why it does that. > > vsyscall.S is an assembly file which depends on asm/offset.h, which > is regenerated each build. But the regeneration is written in a way to > not trigger rebuilds when nothing has changed. That works for everything > else, just apparently not for the vsyscall.S file. Hi Andi, I recall I have a mail from you about this. Last time I looked I could not figure out what was wrong, but let me try again. Could you send me the output of "make V=1" for an otherwise clean compile. 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/