public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Wojciech 'Sas' Cieciwa" <cieciwa@alpha.zarz.agh.edu.pl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: HOWTO build modules in 2.6.0 ...
Date: Mon, 17 Nov 2003 21:33:36 +0100	[thread overview]
Message-ID: <20031117203336.GA1714@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.58L.0311171939150.25906@alpha.zarz.agh.edu.pl>

On Mon, Nov 17, 2003 at 08:00:50PM +0100, Wojciech 'Sas' Cieciwa 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

Hi Sas.
What you really need is the possibility to specify an alternate location
for output files.

Use the following:
make -C /usr/src/linux SUBDIRS=`pwd` O=/users/cieciwa/rpm/BUILD/eagle-1.0.4/linux modules

O=/users/cieciwa/rpm/BUILD/eagle-1.0.4/linux
tell kbuild to locate all files in the specified directory, which must exist.
This is also the location of .config, so make sure to copy that one over.

	Sam

  parent reply	other threads:[~2003-11-17 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 19:00 HOWTO build modules in 2.6.0 Wojciech 'Sas' Cieciwa
2003-11-17 18:05 ` Randy.Dunlap
2003-11-17 18:28 ` David T Hollis
2003-11-17 20:33 ` Sam Ravnborg [this message]
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=20031117203336.GA1714@mars.ravnborg.org \
    --to=sam@ravnborg.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