public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Helge Hafting <helgehaf@idb.hist.no>
Cc: "McHarry, John" <john.mcharry@gemplex.com>, linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
Date: Thu, 21 Jun 2001 12:42:17 +1000	[thread overview]
Message-ID: <6519.993091337@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 20 Jun 2001 09:58:54 +0200." <3B3057BE.4374D4B2@idb.hist.no>

On Wed, 20 Jun 2001 09:58:54 +0200, 
Helge Hafting <helgehaf@idb.hist.no> wrote:
>This is enough if you don't use modules.  If you use modules you
>need to copy them too, which is trickier.  Several good methods
>have been demonstrated, here is another if you can't use the nfs
>approach:
>
>1. If you are running the same kernel revision on the compile machine,
>   temporarily rename /lib/modules/<version> to something else.
>   Yes - this could be dangerous but tend to work well on a "home
>machine"
>2. Do the "make modules_install" on the compile machine.

The correct way of installing for a target machine is to use
  make INSTALL_MOD_PATH=foo modules_install
You need to mkdir -p foo/lib/modules first.  Everything is installed in
foo/lib/modules/`uname -r` instead of /lib/modules so you do not
disturb your compile system.

There is also make INSTALL_PATH to specify where vmlinuz and System.map
are stored for make zlilo and make install.


  reply	other threads:[~2001-06-21  2:42 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
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=6519.993091337@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=helgehaf@idb.hist.no \
    --cc=john.mcharry@gemplex.com \
    --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