Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 7 Oct 2002 10:25:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 7 Oct 2002 10:25:34 -0400 Received: from pizda.ninka.net ([216.101.162.242]:45977 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Mon, 7 Oct 2002 10:25:34 -0400 Date: Mon, 07 Oct 2002 07:24:26 -0700 (PDT) Message-Id: <20021007.072426.93474936.davem@redhat.com> To: kai-germaschewski@uiowa.edu Cc: linux-kernel@vger.kernel.org Subject: Re: kbuild news From: "David S. Miller" In-Reply-To: References: <20021007.010843.130618724.davem@redhat.com> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 837 Lines: 22 From: Kai Germaschewski Date: Mon, 7 Oct 2002 09:22:51 -0500 (CDT) I'll take a look on how to do sparc's btfixup in a similar way, without messing up the common code too much. BTW, the combination kallsyms + btfixup, does that need a particular ordering? No, the kallsyms object file would not need to be seen by the btfixup.o generator. It could therefore be done validly as: 1) build .tmp_vmlinux 2) build btfixup.o 3) build kallsyms 4) link final vmlinux image The order of #2 and #3 could be transposed and that would be fine too. - 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/