From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13944 invoked by uid 1002); 7 Jan 2003 23:04:30 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 9233 invoked from network); 7 Jan 2003 23:04:30 -0000 Date: Tue, 07 Jan 2003 16:59:22 -0600 From: Jyrinx In-reply-to: <1041689680.27164.65.camel@newkid.milsson.nu> To: John Nilsson Cc: gentoo-dev Message-id: <1041980362.4008.5.camel@kryptonitespoon.res.carleton.edu> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.0.8 Content-type: text/plain Content-transfer-encoding: 7bit References: <1041685294.27165.48.camel@newkid.milsson.nu> <1041688369.775.2.camel@gameplay.alek.shacknet.nu> <1041689680.27164.65.camel@newkid.milsson.nu> Subject: Re: [gentoo-dev] [Fwd: [gentoo-admin] Building a second system] X-Archives-Salt: 7e01f9bf-1c69-47a8-865e-691148d8a2bb X-Archives-Hash: f6fb70ce36f08e16d0ba78ec81797d99 > If I do it this way I would have to compile an entire bootstrap > environment for the 486. Also I wouldn't get the benefits of having gcc > optimized for the athlon. > What I would like is to write a simple script to use when upgrading the > server. Change the makefile and compile 486 optimized staticly linked > binaries to packages that are later merged into the server. I'm not much of a hacker, and I don't remember the context, but someone once mentioned using distcc (distributed-computing version of gcc) for this build-on-beefy-computer-for-older-one scenario; that way, you'd build the system relatively quickly, and update it just as quickly, if I'm not mistaken. (Seems like this is a common task ... is there a FAQ or HOWTO for this somewhere?) Jyrinx jyrinx_list@mindspring.com -- gentoo-dev@gentoo.org mailing list