Gentoo Archives: gentoo-dev

From: Arnold deVos <adv@××××××××××××.au>
To: gentoo-dev@g.o
Subject: [gentoo-dev] Re: [Fwd: [gentoo-admin] Building a second system]
Date: Mon, 06 Jan 2003 00:13:31
Message-Id: avagvl$jdl$1@main.gmane.org
In Reply to: Re: [gentoo-dev] [Fwd: [gentoo-admin] Building a second system] by John Nilsson
1 I have exactly the same need. A powerful Athlon building packages for a an
2 older 486 or pentium box (eg firewall or other appliance). I have
3 experimented with the following ideas:
4
5 1 -
6
7 - create a /my486Image hierarchy
8 - setup the /my486Image/etc/make.conf for cross compiling.
9 - export ROOT=/my486image (instead of /)
10 - use emerge from within the host (Athlon) system.
11
12 Unfortunately emerge seems to touch stuff outside of ROOT such as the
13 package db.
14
15 2 -
16
17 - create a normal chroot environment for the 486
18 - mount the Athlon enviroment within this as /hostAlthonImage.
19 - Set the PATH to /hostAthlonImage/bin:/hostAthlonImage/usr/bin etc etc
20 - use emerge (ie /hostAthlonImage/usr/bin/emerge)
21
22 The problem is the ld.so library path. Its tricky to get ld.so to load
23 runtime .so's from /hostAthlonImage and not from the chroot's /usr/lib
24
25 Of these solutions I think (1) is more promising but looks like I need to
26 check the emerge source to find the gotcha's.
27
28 It would be really useful if the fakeroot emerge facility mentioned by
29 drobbins on the gentoo frontpage was available. (I can't find it. Anyone
30 know how to use this feature?)
31
32
33 - Arnold
34
35 "John Nilsson" <john@×××××××.nu> wrote in message
36 news:1041689680.27164.65.camel@××××××××××××××.nu...
37 > If I do it this way I would have to compile an entire bootstrap
38 > environment for the 486. Also I wouldn't get the benefits of having gcc
39 > optimized for the athlon.
40 > What I would like is to write a simple script to use when upgrading the
41 > server. Change the makefile and compile 486 optimized staticly linked
42 > binaries to packages that are later merged into the server.
43 >
44 >
45 > On Sat, 2003-01-04 at 14:52, Timo A. Hummel wrote:
46 > > I don't know if it's the correct list, but I did it as follows to
47 > > compile a pentium optimized system:
48 > >
49 > > I plugged in the 4GB hdd of my Pentium system, created the file systems,
50 > > setup a chroot environment and did the whole gentoo install from there.
51 > > worked like a charm, which was pretty good since I don't have a keyboard
52 > > on my Pentium system. It's pretty straightforward, and shouldn't give
53 > > any problems. Remember to set the make.conf correctly.
54 > >
55 > > cheers,
56 > > Timo
57 > >
58 > >
59 > > On Sat, 2003-01-04 at 14:01, John Nilsson wrote:
60 > > > which is the correct mailing list for this kind of question?
61 > > >
62 > > > ______________________________________________________________________
63 > > >
64 > > > From: John Nilsson <john@×××××××.nu>
65 > > > To: gentoo-admin@g.o
66 > > > Subject: [gentoo-admin] Building a second system
67 > > > Date: 04 Jan 2003 12:52:51 +0100
68 > > >
69 > > > I would like to use my current athlon-xp optimized system to compile a
70 > > > base system for a 486. How do I go about it?
71 > > > I suppose I would have to keep an 486 optimized copy of glibc
72 somewhere, how?
73 > > >
74 > > > It would be nice to have a more or less permanent setup so I can
75 upgrade
76 > > > packages easily later on.
77 > > >
78 > > > --
79 > > > gentoo-admin@g.o mailing list
80 > > >
81 > > >
82 > > >
83 > > >
84 > > > ______________________________________________________________________
85 > > >
86 > > > --
87 > > > gentoo-dev@g.o mailing list
88 > > --
89 > > Timo A. Hummel <timo.hummel@×××.net>
90 > >
91 > >
92 > > --
93 > > gentoo-dev@g.o mailing list
94 > >
95 > >
96 >
97 >
98 > --
99 > gentoo-dev@g.o mailing list
100 >
101 >
102
103
104
105
106
107 --
108 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Re: [Fwd: [gentoo-admin] Building a second system] Bart Verwilst <verwilst@g.o>
[gentoo-dev] Re: [Fwd: [gentoo-admin] Building a second system] kai.grossjohann@uni-duisburg.de (Kai =?iso-8859-1?q?Gro=DFjohann?=)