From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Wojciech 'Sas' Cieciwa" <cieciwa@alpha.zarz.agh.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HOWTO build modules in 2.6.0 ...
Date: Mon, 17 Nov 2003 10:05:20 -0800 [thread overview]
Message-ID: <20031117100520.7b3b5529.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58L.0311171939150.25906@alpha.zarz.agh.edu.pl>
On Mon, 17 Nov 2003 20:00:50 +0100 (CET) "Wojciech 'Sas' Cieciwa" <cieciwa@alpha.zarz.agh.edu.pl> wrote:
|
| Hi,
|
| How can I build kernel modele from other package without root, or copying
| all from /usr/scr/linux/ ??
| When I try build kernel module from user i got error,
|
| [...]
| make[1]: Leaving directory `/users/cieciwa/rpm/BUILD/eagle-1.0.4/driver'
| /usr/bin/make -C /usr/src/linux SUBDIRS=`pwd` modules;
| make[1]: Entering directory `/usr/src/linux-2.6.0'
| HOSTCC scripts/fixdep
| cc1: Permission denied: opening dependency file scripts/.fixdep.d
| make[2]: *** [scripts/fixdep] Error 1
| make[1]: *** [scripts] Error 2
| make[1]: Leaving directory `/usr/src/linux-2.6.0'
| make: *** [adiusbadsl.o] Error 2
| make: Leaving directory `/users/cieciwa/rpm/BUILD/eagle-1.0.4/driver'
|
| How can I solve this problem ??
Current kernel build requires a kernel source tree.
Given that, follow directions in linux/Documentation/kbuild/modules.txt
and .../makefiles.txt.
I have some working examples if you want pointers to them.
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-11-17 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 19:00 Wojciech 'Sas' Cieciwa
2003-11-17 18:05 ` Randy.Dunlap [this message]
2003-11-17 18:28 ` David T Hollis
2003-11-17 20:33 ` Sam Ravnborg
2003-11-17 23:59 ` John Levon
2003-11-18 5:50 ` Sam Ravnborg
2003-11-18 7:11 ` Ian Kent
2003-11-18 13:39 ` John Levon
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=20031117100520.7b3b5529.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=cieciwa@alpha.zarz.agh.edu.pl \
--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
all inboxes | Powered by JetHome®