From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [q] kbuild for private asm-offsets (Re: [PATCH 6/10] lguest code: the little linux hypervisor.) Date: 12 Feb 2007 18:24:13 +0100 Message-ID: <20070212172413.GA40274@muc.de> References: <1171012296.2718.26.camel@localhost.localdomain> <1171012761.2718.40.camel@localhost.localdomain> <1171012827.2718.42.camel@localhost.localdomain> <200702091109.20061.ak@muc.de> <1171024771.2718.129.camel@localhost.localdomain> <20070209141728.GA26749@uranus.ravnborg.org> <1171034599.2718.190.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Date: Mon, 12 Feb 2007 18:24:13 +0100 Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Oleg Verych Cc: Rusty Russell , Sam Ravnborg , virtualization@lists.osdl.org, lkml - Kernel Mailing List , Andrew Morton List-Id: virtualization@lists.linuxfoundation.org > If you will have time for newbie, to explain in a few words, what is it need > for (whole idea, or key detail), and, maybe, why it is generated so ... interestingly: > > asm-offsets.c -> *.s -> *.h > (but this looks like interconnecting C and assembler, obviously) > > I will glad to help providing solution maybe somewhat earlier (well, i'm > trying to understand whole building process, if that matters). The problem is trying to figure out what needs to be done to get multiple asm-offsets.h. -Andi