Subject: Re: How will I build port-dnard from port-cats (etc) ?
To: Todd Whitesel <toddpw@best.com>
From: Chris Gilbert <chris@paradox.demon.co.uk>
List: port-arm32
Date: 04/06/2001 10:34:47
On Friday 06 April 2001 10:08 am, Todd Whitesel wrote:
> As much as everyone wants to abandon the old monolithic arm32 port, it
> should be acknowledged that it did have one very nice feature:
>
> The userland was _absolutely_ identical, and the kernels could all be built
> trivially from any of the machine types. So if you built one of the machine
> types with 'make snapshot', you automatically built _all_ of them.

userland should stay the same.  make snapshot may have to be tweaked to build 
kernels from multiple places, but that should be possible.  May have to 
rename the kernels from GENERIC to CATS_GENERIC.

> What steps (if any!) are being taken to preserve this effort-saving
> feature?

I don't think any have been yet, but I don't see that it's worthwhile to work 
on that till the split is done, and we've got a near final directory 
structure in place.  I assume that the plan is to have something like:
arch/cats
arch/dnard
arch/riscpc (or whatever dir name is decided)
arch/hpcarm (I think this runs the same binaries as arm32, not sure if it can 
be built with standard arm32 tools though?)
arch/ebsa285
arch/rc7500

all of which will probably have a conf/GENERIC.  however it may take time for 
the riscpc dir to have a generic that supports a7000's as well.

The other issue is bootloaders, as we need to supply those that we can, it 
might be worth having a script in arch/x/stand/snapshot that handles building 
and snapshotting the correct bootloader.  or should that be in the distrib 
stuff?

Chris