Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Why linux26-modules before linux26
Date: Mon, 4 Aug 2008 09:02:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0808040901350.7693@localhost.localdomain> (raw)
In-Reply-To: <20080804130121.GB27672@mx.loc>

On Mon, 4 Aug 2008, Bernhard Fischer wrote:

> On Fri, Aug 01, 2008 at 09:34:36PM -0700, Brian Beattie wrote:
> >I have a kernel that does not want to compile the modules before
> >the rest of the kernel.  I've worked around that, but it does raise
> >a question that maybe somebody knows the answer to, why are the
> >makefiles set to compile the kernel-modules so early compared to
> >the rest of the kernel?
>
> This was added by Steven, IIRC. I don't see a reason why the modules
> are built before the kernel.
>
> Steven, can you please explain?

why should it make a difference?  shouldn't kernel modules be
buildable independently from the kernel proper?  AFAIK, all that's
required of the kernel tree is to do the equivalent of "make
modules_prepare", no?

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

  reply	other threads:[~2008-08-04 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02  4:34 [Buildroot] Why linux26-modules before linux26 Brian Beattie
2008-08-04 13:01 ` Bernhard Fischer
2008-08-04 13:02   ` Robert P. J. Day [this message]
2008-08-04 13:31   ` sjhill at realitydiluted.com

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=alpine.LFD.1.10.0808040901350.7693@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox