mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Studying MTD <studying_mtd@yahoo.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: agoddard@purdue.edu, joshk@triplehelix.org, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.0-test1 : modules not working
Date: Wed, 30 Jul 2003 11:02:01 -0700 (PDT)	[thread overview]
Message-ID: <20030730180201.78497.qmail@web20509.mail.yahoo.com> (raw)
In-Reply-To: <20030730080115.28fd5d4f.rddunlap@osdl.org>

I am curious what is the minimum kernel source tree is
required to build external modules.

I dont want to touch my kernel , i want to make
another directory same 'module_test' and want to copy
only required minimum kernel Source tree with modified
scripts's Makefile and kbuild Makefile to build "Hello
World".

Please help me.

Thanks.


--- "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> 
> Sure, 2.6 supports external modules (if you mean
> modules that are
> built outside of the kernel source tree), but for
> now you also
> need a full kernel source tree for the build system
> to reference.
> I.e., you can't build an external module without
> having a full
> kernel source tree installed and configured.
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

  reply	other threads:[~2003-07-30 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  4:37 Studying MTD
2003-07-30  4:51 ` Joshua Kwan
2003-07-30  5:41   ` Studying MTD
2003-07-30  6:21     ` Alex Goddard
2003-07-30  6:50       ` Studying MTD
2003-07-30  7:25         ` Alex Goddard
2003-07-30  7:34           ` Studying MTD
2003-07-30 15:01             ` Randy.Dunlap
2003-07-30 18:02               ` Studying MTD [this message]
2003-07-30 18:50                 ` Richard B. Johnson
2003-07-30 22:08               ` Studying MTD

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=20030730180201.78497.qmail@web20509.mail.yahoo.com \
    --to=studying_mtd@yahoo.com \
    --cc=agoddard@purdue.edu \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®