From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] framework for building modules externally
Date: Tue, 04 Nov 2008 20:55:52 +0200 [thread overview]
Message-ID: <49109AB8.4010509@nic.fi> (raw)
In-Reply-To: <20081101190204.GB4639@thorin>
Robert Millan wrote:
> On Sat, Nov 01, 2008 at 01:32:29PM +0100, Robert Millan wrote:
>> Hi,
>>
>> Attached patch makes it possible to build modules externally, by:
>>
>> - Installing headers in system include dir.
>>
>> - Exporting two ABI tags (a build-time macro and a run-time variable)
>> for run-time comparison.
>>
>> - Exporting a makefile with COMMON_*FLAGS variables.
>
> Looks like I missed some important details. The headers and some macros are
> not enough, as we need to reproduce part of the build system to build a module
> externally. This new patch provides the following:
Interesting idea. However how do you define GRUB ABI :) ? What is it,
kernel, certain set of modules, or how :) ?
Versioning of the modules would be a good idea indeed to make sure
mismatched modules are not tried together.
next prev parent reply other threads:[~2008-11-04 18:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 12:32 [PATCH] framework for building modules externally Robert Millan
2008-11-01 19:02 ` Robert Millan
2008-11-04 18:55 ` Vesa Jääskeläinen [this message]
2008-11-04 19:07 ` Robert Millan
2008-11-04 19:13 ` Vesa Jääskeläinen
2008-11-04 19:39 ` Robert Millan
2008-11-05 6:57 ` Christian Franke
2008-11-05 9:42 ` Robert Millan
2008-11-05 21:41 ` Christian Franke
2008-11-06 14:52 ` __FILE__ (Re: [PATCH] framework for building modules externally) Robert Millan
2008-11-06 21:10 ` Christian Franke
2008-11-07 19:02 ` Robert Millan
2008-11-10 20:39 ` Christian Franke
2008-11-06 14:54 ` [PATCH] framework for building modules externally Robert Millan
2008-11-06 20:43 ` Christian Franke
2008-11-07 19:05 ` Robert Millan
2008-11-08 11:33 ` Robert Millan
2008-11-10 20:44 ` Christian Franke
2009-04-10 23:19 ` phcoder
2009-04-13 13:55 ` Robert Millan
2008-11-05 9:51 ` Robert Millan
2008-11-08 11:29 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49109AB8.4010509@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.