From: Kelledin Tane <runesong@earthlink.net>
To: linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
Date: Tue, 19 Jun 2001 19:24:33 -0500 [thread overview]
Message-ID: <3B2FED41.DD8E2B95@earthlink.net> (raw)
In-Reply-To: <A5F553757C933442ADE9B31AF50A273B028DB4@corp-p1.gemplex.com> <20010619143253.F81548@onesecure.com>
Gabriel Rocha wrote:
> you could always compile on one machine and nfs mount the /usr/src/linux
> and do a make modules_install from the nfs mounted directory...
The way I've always managed this sort of thing is to tar up your kernel source,
transfer it to the "compile box" however you please, then do all the compile
steps except the "make modules_install" and the copying of the kernel image.
Then tar up the compiled source tree, transfer it over to the box you want to
install on, untar it, and do the rest of the steps (the "make modules_install"
and the copying of the kernel image). Just make sure that all the systems
involved have about the same system time, else you'll get the message, "Clock
skew detected. Your build may be incomplete."
One day I managed to get egcs-2.91.66 to compile against glibc-2.2, and I never
had to do that stuff again. ;)
Kelledin
bash-2.05 $ kill -9 1
init: Just what do you think you're doing, Dave?
next prev parent reply other threads:[~2001-06-20 0:20 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 [this message]
2001-06-20 0:42 ` Gabriel Rocha
2001-06-20 7:58 ` Helge Hafting
2001-06-21 2:42 ` Keith Owens
-- 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=3B2FED41.DD8E2B95@earthlink.net \
--to=runesong@earthlink.net \
--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