From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5599 invoked by uid 1002); 6 Jan 2003 00:13:31 -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 12185 invoked from network); 6 Jan 2003 00:13:30 -0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@gentoo.org Path: not-for-mail From: "Arnold deVos" Date: Mon, 6 Jan 2003 11:02:19 +1100 Organization: langdale consultants Message-ID: References: <1041685294.27165.48.camel@newkid.milsson.nu> <1041688369.775.2.camel@gameplay.alek.shacknet.nu> <1041689680.27164.65.camel@newkid.milsson.nu> X-Complaints-To: usenet@main.gmane.org X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: news Subject: [gentoo-dev] Re: [Fwd: [gentoo-admin] Building a second system] X-Archives-Salt: 061a07d4-e568-4301-a348-f1bb2fbd0ecb X-Archives-Hash: f744417bce81369aa85458858f9db046 I have exactly the same need. A powerful Athlon building packages for a an older 486 or pentium box (eg firewall or other appliance). I have experimented with the following ideas: 1 - - create a /my486Image hierarchy - setup the /my486Image/etc/make.conf for cross compiling. - export ROOT=/my486image (instead of /) - use emerge from within the host (Athlon) system. Unfortunately emerge seems to touch stuff outside of ROOT such as the package db. 2 - - create a normal chroot environment for the 486 - mount the Athlon enviroment within this as /hostAlthonImage. - Set the PATH to /hostAthlonImage/bin:/hostAthlonImage/usr/bin etc etc - use emerge (ie /hostAthlonImage/usr/bin/emerge) The problem is the ld.so library path. Its tricky to get ld.so to load runtime .so's from /hostAthlonImage and not from the chroot's /usr/lib Of these solutions I think (1) is more promising but looks like I need to check the emerge source to find the gotcha's. It would be really useful if the fakeroot emerge facility mentioned by drobbins on the gentoo frontpage was available. (I can't find it. Anyone know how to use this feature?) - Arnold "John Nilsson" wrote in message news:1041689680.27164.65.camel@newkid.milsson.nu... > 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. > > > On Sat, 2003-01-04 at 14:52, Timo A. Hummel wrote: > > I don't know if it's the correct list, but I did it as follows to > > compile a pentium optimized system: > > > > I plugged in the 4GB hdd of my Pentium system, created the file systems, > > setup a chroot environment and did the whole gentoo install from there. > > worked like a charm, which was pretty good since I don't have a keyboard > > on my Pentium system. It's pretty straightforward, and shouldn't give > > any problems. Remember to set the make.conf correctly. > > > > cheers, > > Timo > > > > > > On Sat, 2003-01-04 at 14:01, John Nilsson wrote: > > > which is the correct mailing list for this kind of question? > > > > > > ______________________________________________________________________ > > > > > > From: John Nilsson > > > To: gentoo-admin@gentoo.org > > > Subject: [gentoo-admin] Building a second system > > > Date: 04 Jan 2003 12:52:51 +0100 > > > > > > I would like to use my current athlon-xp optimized system to compile a > > > base system for a 486. How do I go about it? > > > I suppose I would have to keep an 486 optimized copy of glibc somewhere, how? > > > > > > It would be nice to have a more or less permanent setup so I can upgrade > > > packages easily later on. > > > > > > -- > > > gentoo-admin@gentoo.org mailing list > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > > -- > > > gentoo-dev@gentoo.org mailing list > > -- > > Timo A. Hummel > > > > > > -- > > gentoo-dev@gentoo.org mailing list > > > > > > > -- > gentoo-dev@gentoo.org mailing list > > -- gentoo-dev@gentoo.org mailing list