From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Studying MTD <studying_mtd@yahoo.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
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 14:50:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307301440170.1250@chaos> (raw)
In-Reply-To: <20030730180201.78497.qmail@web20509.mail.yahoo.com>
On Wed, 30 Jul 2003, Studying MTD wrote:
> 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.
For Intel:
/usr/src/linux-2.6.0
/usr/src/linux-2.6.0/include/linux/*
/usr/src/linux-2.6.0/include/asm-generic/*
/usr/src/linux-2.6.0/include/asm-i386/*
/usr/src/linux-2.6.0/include/asm # Symlink to above
/usr/src/linux-2.6.0/include/math-emu/*
/usr/src/linux-2.6.0/include/net/*
/usr/src/linux-2.6.0/include/pcmcia/*
/usr/src/linux-2.6.0/include/scsi/*
/usr/src/linux-2.6.0/include/video/*
When you compile modules, you use -I/usr/src/linux-2.6.0/include
...on the command line. Remember to -D__KERNEL__ and -DMODULE.
That's all you need for 2.6.0 modules...
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-07-30 18:49 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
2003-07-30 18:50 ` Richard B. Johnson [this message]
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=Pine.LNX.4.53.0307301440170.1250@chaos \
--to=root@chaos.analogic.com \
--cc=agoddard@purdue.edu \
--cc=joshk@triplehelix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=studying_mtd@yahoo.com \
/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®