From: Keith Owens <kaos@ocs.com.au>
To: Maciek Nowacki <maciek@Voyager.powersurfr.com>
Cc: Tom Diehl <tdiehl@pil.net>, linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
Date: Thu, 21 Jun 2001 13:10:40 +1000 [thread overview]
Message-ID: <6827.993093040@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 20 Jun 2001 14:11:20 CST." <20010620141119.A5660@wintermute.starfire>
On Wed, 20 Jun 2001 14:11:20 -0600,
Maciek Nowacki <maciek@Voyager.powersurfr.com> wrote:
>Change MODLIB in $(TOPDIR)/Makefile (e.g. /usr/src/linux/Makefile). I do this
>to compile the kernel and modules without root priviledges at all. make
>modules_install will fail at the end when trying to run 'depmod', but that's
>okay - you can do that yourself:
That is not OK, it requires user hacks and causes errors. Use
make INSTALL_MOD_PATH=foo modules_install
and everything works. Create $(INSTALL_MOD_PATH)/lib/modules first.
next prev parent reply other threads:[~2001-06-21 3:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 20:32 How to compile on one machine and install on another? McHarry, John
2001-06-19 20:35 ` Alan Cox
2001-06-19 20:55 ` Tom Diehl
2001-06-19 21:04 ` Steven Walter
2001-06-19 21:11 ` Raphael Manfredi
2001-06-19 21:50 ` John R Lenton
2001-06-23 4:53 ` Anuradha Ratnaweera
2001-06-20 20:11 ` Maciek Nowacki
2001-06-21 3:10 ` Keith Owens [this message]
2001-06-19 21:32 ` Gabriel Rocha
2001-06-19 21:45 ` Eli Carter
2001-06-19 21:53 ` Gabriel Rocha
2001-06-19 22:42 ` Mike Castle
2001-06-20 0:24 ` Kelledin Tane
2001-06-20 0:42 ` Gabriel Rocha
2001-06-20 7:58 ` Helge Hafting
2001-06-21 2:42 ` Keith Owens
2001-06-19 21:04 McHarry, John
[not found] <fa.o4pbsqv.26md2n@ifi.uio.no>
[not found] ` <fa.go24tnv.1v60h9a@ifi.uio.no>
2001-06-20 2:23 ` John Weber
2001-06-20 2:50 ` Mike Castle
2001-06-20 2:58 ` Keith Owens
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=6827.993093040@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=maciek@Voyager.powersurfr.com \
--cc=tdiehl@pil.net \
/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;
as well as URLs for NNTP newsgroup(s).