[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] Re: [Fwd: [gentoo-admin] Building a second system]
From:       "Arnold deVos" <adv () langdale ! com ! au>
Date:       2003-01-06 0:02:19
[Download RAW message or body]

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" <john@milsson.nu> 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 <john@milsson.nu>
> > > 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 <timo.hummel@gmx.net>
> >
> >
> > --
> > gentoo-dev@gentoo.org mailing list
> >
> >
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>





--
gentoo-dev@gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]