From: Ben Pfaff <blp@cs.stanford.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: slow module build--what am I doing wrong?
Date: Mon, 29 Jan 2007 18:06:06 -0800 [thread overview]
Message-ID: <87ejpdi7zl.fsf@blp.benpfaff.org> (raw)
In-Reply-To: 87ps8xicsd.fsf@blp.benpfaff.org
Ben Pfaff <blp@cs.stanford.edu> writes:
> When I modify a source file or two that belong to a particular
> module, and then rebuild just that module with "make
> dir1/dir/module.ko" (e.g.), the build system spends a couple of
> minutes grinding away on "MODPOST" operations. Am I doing
> something wrong? Is there a way to avoid this? It slows down my
> build-and-test cycle quite a bit.
I was privately emailed a suggestion to use "make M=dir1/dir"
instead of "make dir1/dir/module.ko". It helps a great deal.
--
Ben Pfaff
blp@cs.stanford.edu
http://benpfaff.org
prev parent reply other threads:[~2007-01-30 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 0:22 slow module build--what am I doing wrong? Ben Pfaff
2007-01-30 2:06 ` Ben Pfaff [this message]
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=87ejpdi7zl.fsf@blp.benpfaff.org \
--to=blp@cs.stanford.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox