From: John R Lenton <john@grulic.org.ar>
To: linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
Date: Tue, 19 Jun 2001 18:50:33 -0300 [thread overview]
Message-ID: <20010619185033.A2970@grulic.org.ar> (raw)
In-Reply-To: <Pine.LNX.4.33.0106191646330.17727-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0106191646330.17727-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
On Tue, Jun 19, 2001 at 04:55:10PM -0400, Tom Diehl wrote:
>
> What is the best way to install the modules? Is there a directory _all_ of
> the modules exist in b4 you do "make modules_install". I usually end up
> setting EXTRAVERSION to something unique and doing a make modules_install.
> That way it does not hose up the modules for the build machine.
> Is there a better way?
make-kpkg takes care of all that for you (it's part of kernel-package)
--
John Lenton (john@grulic.org.ar) -- Random fortune:
No doubt Jack the Ripper excused himself on the grounds that it was
human nature.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-06-19 21:49 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 [this message]
2001-06-23 4:53 ` Anuradha Ratnaweera
2001-06-20 20:11 ` Maciek Nowacki
2001-06-21 3:10 ` Keith Owens
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=20010619185033.A2970@grulic.org.ar \
--to=john@grulic.org.ar \
--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;
as well as URLs for NNTP newsgroup(s).